Re: Authenticate to slapd using attribute other than DN

Use a SASL mechanism that supports the desired credential form. At 04:13 PM 6/5/2006, ryan woodsmall wrote: >Forgive me if I'm missing something blatantly obvious, but I'm >nearing completion on a project to set up the OpenLDAP slapd to proxy >against MS Active Directory servers. This in itse

Re: Authenticate to slapd using attribute other than DN

--On Monday, June 05, 2006 6:13 PM -0500 ryan woodsmall <[EMAIL PROTECTED]> wrote: Forgive me if I'm missing something blatantly obvious, but I'm nearing completion on a project to set up the OpenLDAP slapd to proxy against MS Active Directory servers. This in itself was a pretty large t

Authenticate to slapd using attribute other than DN

Forgive me if I'm missing something blatantly obvious, but I'm nearing completion on a project to set up the OpenLDAP slapd to proxy against MS Active Directory servers. This in itself was a pretty large task, but I've got something working nicely, and I'm most of the way there. I have mu

Re: LDAP_DEPRECATED

At 08:14 AM 6/6/2006, Lise Didillon wrote: >I use now openldap-2.3.19. >Why do I have to "#define LDAP_DEPRECATED 1" in my program (writen for >openldap 2.0.27) to use ldap_init, ldap_add, ldap_add_s, ldap_bind etc?? The requirement for the defining this macro to use deprecated interfaces is

Re: Connection failures from OS X, appears to be TLS-related

Ben Beuchler wrote: On 5/22/06, Aaron Richton <[EMAIL PROTECTED]> wrote: > Care to share the ACL you're using? I've tried both of these: In the global section (before any "database" lines), first access line: access to dn.exact="" attrs=supportedSASLMechanisms by * none So w

Re: Connection failures from OS X, appears to be TLS-related

--On Tuesday, June 06, 2006 3:13 PM -0500 Ben Beuchler <[EMAIL PROTECTED]> wrote: However, that's a little disconcerting. What are the default permissions on this "metadata" section of the tree? Is 'by * read' a reasonable choice? I allow * by * read, and haven't found that to be a pr

Re: Connection failures from OS X, appears to be TLS-related

On 5/22/06, Aaron Richton <[EMAIL PROTECTED]> wrote: > Care to share the ACL you're using? I've tried both of these: In the global section (before any "database" lines), first access line: access to dn.exact="" attrs=supportedSASLMechanisms by * none So with that in place, I

LDAP_DEPRECATED

hello I use now openldap-2.3.19. Why do I have to "#define LDAP_DEPRECATED 1" in my program (writen for openldap 2.0.27) to use ldap_init, ldap_add, ldap_add_s, ldap_bind etc?? (I see that in ldap.h) The only thing I see in the man ldap (3) is that the library in ldap version 2 by default,

Re: ppolicy (how to get hands on the password policy response)

Howard Chu wrote: Prakash Velayutham wrote: Hi, I would like to know how to enable the password policy controls from the server side. I have ppolicy overlay enabled in my slapd.conf, but when I login as a user whose password has expired (during one of the grace logins enabled in the server s

Re: Weird problem importing data to an OpenLDAP Server

Hi, Andres Tarallo <[EMAIL PROTECTED]> writes: > I'm using OpenLDAP version 2.2.27, from SuSE RPMs, in SuSE 10.0. We have > an Old SuSE Email Server and we're dumping soem of the attributes of > it's users and importing them to the corresponding users in the New LDAP > Server. > > With the data

Re: Weird problem importing data to an OpenLDAP Server

On Mon, 2006-06-05 at 18:35 -0300, Andres Tarallo wrote: > I'm using OpenLDAP version 2.2.27, from SuSE RPMs, in SuSE 10.0. We have > an Old SuSE Email Server and we're dumping soem of the attributes of > it's users and importing them to the corresponding users in the New LDAP > Server. > > With