Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Secure Messaging resources
Secure messaging
The steps to take to secure asynchronous messaging.
Security for messaging is enabled only when WAS administrative security is enabled. In this case:
- JMS connections made to a messaging provider are authenticated.
- Access to JMS resources owned by a messaging provider is controlled by access authorizations.
- Requests to create new connections to a messaging provider must include a user ID and password for authentication.
- The user ID and password do not have to be provided by the application.
Standard Java EE Connector Architecture (JCA) authentication is used for a request to create a new connection to a messaging provider. If authentication is successful, the JMS connection is created; if authentication fails, the connection request is ended.
Notes:
- User IDs that are longer than 12 characters cannot be used for authentication with the V5 default messaging provider or with a WebSphere MQ network. For example, the default Windows user ID "Administrator" is not valid for use in this context because it contains 13 characters.
- To enable the WebSphere MQ messaging provider to connect in bindings transport mode to WebSphere MQ, you set theTransport type parameter on the WebSphere MQ queue connection factory to BINDINGS, and you configure the WebSphere MQ messaging provider with native libraries information.
We must also choose one of the following options:
- If you are using security credentials (user ID and password), ensure that the user specified is the current logged-on user for the WAS process, otherwise the following WebSphere MQ JMS Bindings authentication exception message is generated: MQJMS2013 invalid security authentication supplied for MQQueueManager.
- If you are not using security credentials, ensure that neither the Component-managed Authentication Alias nor the Container-managed Authentication Alias properties are set on the connection factory.
To secure your asynchronous messaging, complete one or more of the following steps:
Procedure
- Enable security.
- Use JCA authentication to create a new connection to the messaging provider.
If the resource authentication (res-auth) property is set to Application, set the Component-managed Authentication Alias property on the connection factory. If the application that tries to create a connection to the messaging provider specifies a user ID and password, those values are then used to authenticate the creation request. Otherwise, the values defined by the Component-managed Authentication Alias property are used. If you do not set the Component-managed Authentication Alias property on the connection factory, a runtime JMS exception message is generated when an attempt is made to connect to the messaging provider.
- Authorize access to messages stored by the default messaging provider.
Access to these messages is controlled by authorization to access the service integration bus destinations on which the messages are stored. For information about authorizing permissions for individual bus destinations, see Administer destination roles.
- Configure security for message-driven beans that use listener ports
Complete this step if you are working with a message-driven bean and are configuring a message-driven bean listener under the Message Listener Service.
Related
Configure security for message-driven beans that use listener ports
Configure security for message-driven beans that use activation specifications
Configure authorization security for v5 default messaging
Service integration security
Configure the WebSphere MQ messaging provider with native libraries information