[Date Prev][Date Next] [Chronological] [Thread] [Top]

AW: LDAP proxy for AD -- still no solution

Hello Nazeer,

>Hi All,
>I progressed further, but still haven't reached stage where I can use
AD account.
>Through, the proxy setup I could able to query ldap, but unable to use
it for authentication. For example,
>ldapsearch -x -h ldapserver -LLL -b dc=internal,dc=phg,dc=com,dc=au
>is Successful, but id nazeerm fails (returns id: nazeerm: No such
>Here is ldap.conf file on client machine.

We had a similar problem (on Solaris though), the problem was that the
ACLs for slapd were too tight.

Bear in mind that we use OpenLDAP as internal user management tool (in a
DMZ), so security isnt too much an issue.

We now use:

access to * by * read

access to attrs=userpassword by self write by * read by anonymous auth
access to dn.subtree="<subtree for the group mapping>" by * read by *

(I know this is partly redundant, never got to change it on the
production system since we do not have downtimes very often).

Access to userpassword was necessary for "su" commands to succeed.
Access to the group subtree was necessary for getting the proper
user-to-group mapping via the "id" or "getent" commands.

I would suggest to start with widely opened gates and then gradually
closing them as far as you can.

Hope this helps you a bit.