+

Search Tips   |   Advanced Search

Configuring security for message-driven beans that use activation specifications

Use this task to configure resource security and security permissions for message-driven beans.

Messages handled by message-driven beans 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 EJB component security. For more information about configuring security for the application, see Assembling secured applications.

Connections used by message-driven beans can benefit from the added security of using JCA container-managed authentication. To enable the use of JCA container authentication aliases and mapping, define an authentication alias on the activation specification that the message-driven bean is configured with. If defined, the message-driven bean uses the authentication alias for its JMSConnection security credentials instead of any application-managed alias.

To set the authentication alias, we can use the console to complete the following steps. This task description assumes that we have already created an activation specification. To create a new activation specification, see the related tasks.


Related tasks

  • Configure security for message-driven beans that use listener ports
  • Configure an activation specification for the default messaging provider