A common requirement for enterprises is to have the ability for the users in their Active Directory to be able to login into Liferay Portal(s) with Active Directory credentials. This can be achieved in Liferay by using the Liferay LDAP tool that comes bundled together with Liferay Community Edition. This tool works well when you just want to allow AD users to login with AD credentials into Liferay. There are a number issues with exporting user from Liferay to AD but lets just focus on import for now.
Liferary integrates with AD through importing the users. This means that if user wants to be able to login into the portal his record has to be present in the Liferay User database. So whenever you enter your credentials into the login screen of a Lifray Portal integrated with AD, the LDAP tool would always check your credentials entered againsts the AD and if there is a match you will be logged in. Lets have a look at the configurations required to enable this.
- Login into Liferay as an admin user.
- Go to Control Panel -> Portal Settings -> Authentication -> LDAP.
- Click Add, this will open ‘ADD LDAP Server’ page.
- Under Server Name – <an appropriate name for the configuration>
- Base Provider URL: <the URL of the LDAP Server>
- Use port 636 if the AD allows secure LDAP connections
- Otherwise, port 389 for insecure LDAP connections.
- Base DN: <enter the distinguished name of the Base OU where Liferay LDAP would search for users>
- Principal: <the username of the user you’d use to connect with AD>
- Credentials: <password>
- If you click ‘Test LDAP Connection’ now, you should see a pop up suggesting that Liferay has successfully connected to the LDAP server. If the message suggests failure to connect, then please make sure your configurations are correct before moving forward.
- Authentication Search filter: This is the filter that Liferay LDAP would use to search for a user in AD. So if you set it to (mail=@email_address@) then liferay would search would search for the user with the supplied email address in AD. You can set multiple filters on this, for example (&(objectCategory=user)(mail=@email_address@)) would also check that the objectCategory is user in addition to matching the email address.
- Import Search filter: This filter is used by Liferay LDAP tool for mass import of users. I would recommend to not use mass import if you dont have to and let import only happen at user login. For example, if you set this filter to (objectCategory=user), the LDAP tool will import all users that have objectCategory of user.
- Screen Name: cn (Screen Name is usually mapped to the cn attribute in AD, you could map it to sAMAccountName as well depending upon your requirements).
- Password: userPassword
- Email Address: mail
- First Name: givenName
- Last Name: sn
- Job Title: title
- If you click ‘Test LDAP Users’ you should see a list of users in a pop up. If you dont see a pop up or there are no users in the pop up, this means that the configurations you entered are not correct. Please go back and check your configurations.
- Please make sure that the export section is blank as we are not exporting users from Liferay to AD.
- Press Save.
All your configurations should now be saved in PortalPreferences tables in Liferay database.
Go back to the LDAP tab now and make sure you have checked Enabled and Required checkboxes and save your changes.
If you log out and log in with a user that exists in AD you should be able to login if you’ve enterd the correct credentials.