WAS v8.5 > Secure applications > Secure Service integration > Secure service integration > Enable client SSL authenticationConfigure a bus to allow client SSL authentication
We can configure a service integration bus to enable connecting client JMS applications to authenticate using SSL certificates.
You must ensure the following tasks have been completed:
- Administrative security is enabled. For more information, see Enable security.
- A stand-alone LDAP user registry has been configured for storing user and group IDs. To access the user registry, you must know a valid user ID that has the administrative role, and password, the server host and port of the registry server, and the base distinguished name (DN). For more information, see Configure LDAP user registries.
- Bus security is enabled. For more information, see Disable bus security.
- JMS client applications have been configured to authenticate using client SSL certificates.
To allow connecting JMS application clients to authenticate to the bus using client SSL certificates, define an SSL configuration. There are two parts to this task. First we use the dmgr console to map SSL certificates to entries in the LDAP user registry. Secondly, you create a unique SSL configuration for each endpoint address for which to use client SSL authentication. Do not use the default SSL configuration for the bus.
- Use the dmgr console to define certificate filters to map an SSL certificate to an entry in the LDAP server. For more information, see Create an SSL configuration. The client SSL certificate is mapped to a user ID in the user registry.
- Create a separate SSL configuration file for each endpoint address for server, bus member or cluster on the bus, and select that client authentication is required. For more information, see Create an SSL configuration
Results
The bus is configured to allow client SSL authentication.
Connect JMS client applications can now authenticate to the bus using client SSL certificates.