If you are using messaging security, there are a number of considerations that apply to service integration buses.
You can enable bus security so that access to the bus itself and to all destinations on the bus must be authorized. For bus security to be enabled, WebSphere global security must also be enabled. Refer to Messaging security for more information.
When a bus is created, an initial set of authorization permissions is created. These permissions grant all authenticated users access to the bus and to all local destinations. Refer to Administering authorization permissions for more information about controlling access to bus resources.
When bus security is enabled, you must set the Inter-engine authentication alias property to control the authentication of messaging engines joining the bus and for secure communication between messaging engines. Similarly, the Mediations authentication alias property is used for mediations that access the bus. Refer to Adding a bus for further information.
In the routing definitions for connections to foreign buses, the user ID applied to messages entering or leaving the foreign bus can be replaced by values specified by the Inbound user ID and Outbound user ID properties. For more information, see Adding a foreign bus.
The Authentication alias property of the service integration bus link is used for authentication of access to a foreign bus. For more details, see Adding a service integration bus link.