JMS security considerations


Security for asynchronous messaging is enabled only when global security is enabled. J2C authentication can be used to provide a username/password for authentication.

You can specify a Component-managed Authentication Alias or a Container-managed Authentication Alias for each connection factory, depending on the resource authentication (res-auth) setting:

If you want to use a WebSphere MQ JMS connection when using Bindings transport mode, you set the property Transport type of BINDINGS on the WebSphere MQ Queue Connection Factory. You must also choose one of the following options:

For a clustered and distributed system that spans multiple machines, you will not want to use a Tranport type of BINDINGS. Rather, use Transport type of CLIENT.