Access control for multiple buses

Buses must be able to exchange messages securely with each other and with WebSphere® MQ.

When a message is sent to a destination in a foreign bus, authorization permissions are checked in two stages:

  1. When the message is sent, a check is made that the sender has permission to send messages to the foreign bus.
  2. When the message enters the foreign bus, a check is made that the sender is allowed to access the destination by checking against the permissions defined on the foreign bus.

Messages are sent to a foreign destination by using either a proxy definition of the foreign destination itself or a definition of the foreign bus. Foreign destination and foreign bus definitions both have authorization permissions that determine whether the user can send messages to the foreign bus. Foreign destination definitions allow the permissions to be defined on a destination by destination basis. Foreign bus definitions provide defaults when a foreign destination definition does not exist for the specific destination being used.

It is important to understand that authorization permissions associated with a foreign bus or foreign destination control whether a user can send messages to the foreign bus. When the message reaches the foreign bus another check is made to determine whether the message can proceed to the destination itself, this check uses the authorization permissions defined by the administrator on the foreign bus itself.

The authorization check that takes place when the message enters the foreign bus is based on the user ID that is stored in the message, and this is initially set to the user ID of the sender. If the user ID in messages entering or leaving the foreign bus is replaced by values specified by the Inbound user ID or Outbound user ID properties, the check is performed on the Inbound or Outbound user ID, not the original user ID.

The checks on Inbound and Outbound user IDs also apply when messages are routed through multiple buses, and when messages are being sent to a WebSphere MQ network.

Tip: You specify Inbound and Outbound user IDs when you create a routing definition (virtual link) for the link to a foreign bus. For further information, see Creating a routing definition.

If secure buses are linked, the link between them should be secure. To protect data transmitted along the virtual link between buses by using SSL or HTTPS, you need to define the required transport chains and then reference the transport chain name.




Related concepts
Learning about service integration security
Related tasks
Administering messaging security
Creating a routing definition
Adding a foreign bus
Related reference
Creating a service integration bus using the wsadmin tool
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=cjr0410_
File name: cjr0410_.html