Securing service integration

Messaging security protects a service integration bus from unauthorized access. When administrative security is enabled for the application server, by default messaging security is also enabled for the bus. You can also manually administer messaging security for the bus.

Before you begin

Review the security requirements for the bus. For guidance, see Service integration security planning.

About this task

Providing administrative security is also enabled, messaging security enforces a security policy that prevents unauthorized client applications from connecting to the bus, and accessing bus resources. There might be circumstances when you do not require messaging security, for example on a development system. In this case, you can disable messaging security.
You can customize the security configuration for the bus by using the administrative console, or wsadmin scripting commands. The security configuration controls the following aspects of bus security:
  • Authorizing groups of users in the user registry to undertake selected operations on bus destinations.
  • The transport policies that maintain the integrity of messages in transit on the bus.
  • The use of global, and multiple custom security domains.
  • The integrity of links between messaging engines, foreign buses and databases.