Ensure that the X.500 directory server is running.

Start Fuse ESB by entering the following command in a terminal window:

> servicemix

Create a Blueprint configuration file called ldap-module.xml.

Copy Example 8.1 into ldap-module.xml.

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
  xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"
  xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0">

  <jaas:config name="karaf" rank="1">
    <jaas:module className="org.apache.karaf.jaas.modules.ldap.LDAPLoginModule"
                 flags="required">
      initialContextFactory=com.sun.jndi.ldap.LdapCtxFactory
      connection.username=uid=admin,ou=system
      connection.password=secret
      connection.protocol=
      connection.url=ldap://localhost:10389
      user.base.dn=ou=users,ou=system
      user.filter=(uid=%u)
      user.search.subtree=true
      role.base.dn=ou=roles,ou=system
      role.name.attribute=cn
      role.filter=(member=uid=%u)
      role.search.subtree=true
      authentication=simple
    </jaas:module>
  </jaas:config>
</blueprint>

This login module creates a JAAS realm called karaf, which is the same name as the default JAAS realm used by Fuse ESB. By redefining this realm with a rank attribute value greater than 0, it overrides the standard karaf realm which has the rank 0. For more information on configuring a JAAS realm see Defining JAAS Realms.

For a detailed description of configuring Fuse ESB to use LDAP see Enabling LDAP Authentication.

To deploy the new LDAP module, copy the ldap-module.xml into the Fuse ESB deploy/ directory.

The LDAP module is automatically activated.

Test the new LDAP realm by connecting to the running container using the Fuse ESB client utility.

1. Open a new command prompt.

2. change directory to the Fuse ESB install directory.

3. Enter the following command to log on to the running container instance using the identity janedoe:

   client -u janedoe -p secret

   You should receive the following message:

   Authentication failure

   This fails because janedoe does not have the admin role which is required for using the remote console.

4. Enter the following command to log on to the running container instance using the identity jdoe:

   client -u jdoe -p secret

   You should successfully log into the container's remote console because jdoe does have the admin role.

Log off the remote console by entering the logout command.