[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
backend ldap and ActiveDirectory - bind using samAccountname
- To: openldap-software@OpenLDAP.org
- Subject: backend ldap and ActiveDirectory - bind using samAccountname
- From: Arthur Fonzarelli <contemptuous@gmail.com>
- Date: Fri, 14 Jan 2005 15:13:24 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=fpvev2Rl5YKUhMMqhGDSeabt8F+Xe6Cbnc9AR2F/wl0PgvMys5FWtJ1u8QZ4RH87k0siNa5UqQTHR9DLu5qJLFicQGIfAr65HSwD+zxJUQM61HjiFkwUdvOha0k6vp7EWNDUNMY7SC26ANLtrGABbmnsEb43soWLu1BQv8qjcvk=
I am using openldap-2.2.15 with SASL (supports NTLM/GSSAPI)
I have backend ldap working, currently users bind with their DN.
Problem is that M$ Entourage does not allow bind with a DN when using
the exchange plugin.
What it does use is the nt username/password/domain combination.
Does anyone know how i can keep my backend ldap but allow the users to bind with
the nt domain\username password vlaues ?