WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Destination security

When messaging security is switched on, users must have permission to access destinations, including temporary destinations. If a message needs to be routed on from one destination to one or more other destinations, the user must have permission to access all the destinations concerned.

Authorization checks on destinations

To allow a user access to a destination, you must give them the required authorization permissions by assigning them to the appropriate roles, depending on what activity they need to perform. Role assignments for a destination are defined on the bus that owns the destination and all messaging engines on the bus have access to them.

The following roles, which are described in Role-based authorization, are available for destinations:

Temporary destinations

Temporary destinations are created at run-time and can be used straight away. The names of temporary destinations include a prefix that identifies the permanent prefix destination on which the temporary destination is based. The prefix is specified in the connection factory.

When a temporary destination is created, an authorization check is performed to ensure that the user is in the Creator role on the corresponding prefix destination.

Once created, a temporary destination has the same role assignments as the permanent prefix destination on which it is based. To allow users to access a temporary destination, you must assign them to the appropriate roles on the prefix destination.

Multiple destinations

When a message arrives at its initial destination, it may be routed on to one or more other destinations before it is read (consumed) by the receiving application. This can happen, for example, if there is a mediation on the initial destination. When the message is sent to the initial destination, an authorization check is performed to ensure that the sender has permissions to send messages to that destination. The sender's user name is also added to the message.

If the message is routed on to another destination, another authorization check is performed to ensure that the user name in the message has permission to send to the destination to which it is being routed. Because the routing can be dynamic, this check takes place when the message is routed on, not when it is initially sent.

If the message is routed on by a mediation, the mediation may also replace the user name in the message with the name of the mediation user. If that happens, the authorization check will use the name of the mediation user rather than the name of the original sender, that is, it will use whichever user name is stored in the message.

Related concepts
Bus destinations
Temporary destinations
Transactionality in mediations
Related tasks
Learning about bus destinations
Administering messaging security
Administering destination roles
Configuring a destination forward routing path
Configuring a destination reverse routing path

Concept topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\concepts\cjr0430_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)