Secure access to a foreign bus
We can secure the link between a local bus and a foreign bus.
Before we can secure the link between a local bus and a foreign bus, there must be foreign bus connection on the local bus, and therefore a link between the buses.
This task summarizes the significant tasks to secure the link between a local bus and a foreign bus. For more general information about service integration bus security, see Secure service integration.
When we create a foreign bus connection, there are some options to secure the connection during that procedure.
Tasks
- Enable security on the service integration bus and the foreign bus. See Secure buses.
- Secure the link between the buses. See Secure messages between messaging buses.
- Grant access to the local bus for users who will be sending messages to the foreign bus. See Administer the bus connector role.
- Grant access to the foreign bus for users who will be sending messages to it. See Administer foreign bus roles.
- Optional: Give users access to foreign or alias destinations that will forward messages to a foreign bus. See Administer destination roles.
Related:
Foreign buses Direct and indirect routing between service integration buses Disable bus security Enable client SSL authentication Administer authorization permissions Secure messages between messaging buses Secure links between messaging engines Controlling which foreign buses can link to your bus Secure database access Secure mediations Administer the bus connector role Configure buses Secure buses Add unique names to the bus authorization policy Administer permitted transports for a bus