Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Integrate with ldap


Published on

Integrate with ldap

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Integrate with ldap

  1. 1. Integrate with LDAP
  2. 2. Obtain LDAP parameters - Step 1 To obtain LDAP Parameters, a request has to be sent to LDAP admin for the following details – • The LDAP host and listening port • The LDAP user account credentials which is used to connect the LDAP by the console • Structure of the LDAP tree that stores user and group information for console users 2
  3. 3. Set up users and groups on LDAP - Step 2 Create groups in the LDAP and add all the users based on their permission like Administrator, System Administrator, Developer and Monitors 3
  4. 4. Create groups on MMC - Step 3 Create groups on MMC with similar name to gain access to the LDAP database 4
  5. 5. Enable the LDAP Spring profile - Step 4 • Navigate to the following directory: $MULE_HOME/apps/mmc/webapps/mmc/WEB-INF • Locate the file web.xml • Find the below parameter - <param- name></param-name> • Modify by adding ldap as a string – <param-value>tracking-h2,env- derby,ldap</param-value> 5
  6. 6. Enable LDAP on the console - Step 5 • Navigate to the following directory: $MULE_HOME/apps/mmc/webapps/mmc/WEB-INF/classes • Locate the file • Modify following values • Change providerURL, cn, ou and dc to match the ldap tree • providerURL=ldap://LDAPHost:389/ • MMC user/password to use for MMC to authenticate users on login. These credentials can be used to for MMC to connect to the LDAP server • userDn=cn=mmc,dc=company,dc=com password=mmcadmin • activeDirectory integration, the attribute of uid, sAMAccountName can be set • usernameAttribute=uid • base context to search for users within the LDAP tree (search subtree is in true) • userSearchBaseContext=ou=people,dc=company,dc=com 6
  7. 7. Enable LDAP on the console (Cont.) • filter expression used to find entries in the LDAP database that match a particular user • userSearchFilterExpression=(uid={0}) • base context in the LDAP database in which the console will search for users to list in the admin pages, change ou and dcto match the ldap tree. The LDAP tree structure needs to be changed based on the requirement to view the list of users in Console • userSearchBase=ou=people,dc=company,dc=com • Users can be searched by determining the”key-value”. In the default scenario, it will look for objectclass=person. The attribute used to search for users on the LDAP server • userSearchAttributeKey=objectclass • Value of the attribute is used to search for users on the LDAP server. In the LDAP tree all the users should be of object type “person” which are being configured • userSearchAttributeValue=person • “Dn” is used to search for groups to which the user belongs ,ou and dc has to be changed to match the ldap tree • roleDn=ou=groups,dc=company,dc=com groupSearchFilter=(member={0}) 7
  8. 8. Place Jar file - Step 6 • Navigate to the following directory: $MULE_HOME/apps/mmc/webapps/mmc/WEB-INF/lib • Place the jar file called as "spring-ldap-1.3.1.RELEASE-all.jar". Restart MMC • Restart the Mule Management Console. 8