Configure security for message-driven beans
Use this task to configure resource security and security permissions for message-driven beans.
Overview
Messages arriving at a listener port have no client credentials associated with them. The messages are anonymous.
To call secure enterprise beans from a message-driven bean, the message-driven bean needs to be configured with a RunAs Identity deployment descriptor. Security depends on the role specified by the RunAs Identity for the message-driven bean as an EJB component.
For more information about EJB security, see Enterprise bean component security. For more information about configuring security for your application, see Assembling secured applications.
JMS connections used by message-driven beans can benefit from the added security of using J2C container-managed authentication. To enable the use of J2C container authentication aliases and mapping, define a J2C container-managed alias on the JMS connection factory definition that the MDB is using to listen upon (defined by the Connection factory JNDI name property of the listener port). If defined, the listener uses the container-managed authentication alias for its JMSConnection security credentials instead of any application-managed alias. To set the container-managed alias, use the administrative console to complete the following steps:
- To display the listener port settings, click Servers-> application_server->
Message Listener Service-> Listener Ports-> listener_port
- To get the name of the JMS connection factory, look at the Connection
factory JNDI name property.
- Display the JMS connection factory properties. For example, to
display the properties of a queue connection factory provided by the embedded
WebSphere JMS provider, click Resources-> WebSphere JMS Provider-> (In
content pane, under Additional Properties) WebSphere Queue Connection Factories-> connection_factory
- Set the Container-managed Authentication Alias property.
- Click OK
Configuring message listener resources for message-driven beans