Asked By
Jho Hemley
0 points
N/A
Posted on - 01/05/2012
I’ve just upgraded my LDAP authentication module from 2.1.5 to 2.1.6 and in log window, I observed a strange behavior of the said app. Before, upgrading to 2.1.6, auth_ldap can get information only in {ldap_servers}, but in my current version ejab start contacting sub domain controllers which makes nearly DOS. Besides, whenever a user tries to log-in, ejab starts connecting to all DC controller, including no defined domains, even if they’re restricted to managing sub domains only. If you have more than 20 DC with weak support system and X000 users logging in at the same time, this will definitely create a big mess. Can anyone teach me how to force ejab to make authentications via defined LDAP servers? Thanks a bunch in advance.
Issue on Upgrading LDAP Authentication Module 2.1.5 to 2.1.6
The following are the main steps that will help you make authentications using the LDAP servers:
-
First you will need to enable the communication between the LDAP server and the LDAP Authentication provider that you are using.
-
After you have done that, you will need to configure the options that control how the LDAP Authentication provider will be used to search the LDAP directory.
-
You will then need to specify where in the LDAP directory structure users have been located, and then specify where groups are located.
-
Once you have done that, you will need to define how members of a group are located.
-
And then you will choose the LDAP Authentication provider which is a match to your LDAP server and then create an instance of the provider in your security realm.
-
The next thing that you will do is to configure the provider-specific attributes of the LDAP Authentication through the Administration Console.
-Mathew Stone
Â
