TOPIC:

I wonder if someone could explain me what the second ldap filter is.

I guess the use of the main filter is this:
When a user tries to log in xerte the user provides a <username> and a <password>.
The username will be used to check whether he is accepted or not.
In case of ldap authentication that username will be used to search for a matching entry in a directory.
In order to know what attribute the username is associated with you specify the LDAP main filter.
e.g. If ldap main filter is uid, the directory will be searched after until an entry is found with attribute uid=<username>, the password associated will be checked with the <password> provided by the user at login. If the match is OK, the ldap server will send a OK and allow to retrieve the first name and the surname of the user.

I am right this far?


What use then is the ‘ldap second filter’?

The second attribute (and I think we should use a different name) is used if no bind password is given. Then the second filter s used to search the ldap tree, and then a bind is attampted with the value of that attribute as username, and the given password as the password.

It is NOT used if a bind password is given.

OK,

Is there a way I can set LDAP search filters in Xerte?
e.g. If I want only a known set of users to be authenticated through ldap?
Something like:
(|(uid=user.0)(uid=user.1)(uid=user.2))

Bruno

I guess at
Site Administration, LDAP settings
"The LDAP main filter"
should be called
"attribute type matching the username"