Messaging identities

Given Alasdair has been kind enough to include me in the acknowledgements, that guarantees him a plug for his developerWork’s comment line entitled “Connect an application to the default messaging provider using the run-as identity“. This describes how to connect to the default messaging provider in WebSphere Application Server using the application’s current runtime run-as identity rather than, as is usually the case, the credentials administratively associated with the connection factory or resource reference. As always, just because something is possible, doesn’t mean you should do it, so please head Alasdair’s comments about what to consider before implementation.

Comments are closed.