Re: LDAP authentication changes

2008-11-16 Thread Tomas Friml
Hm, tried put it in the brackets, restarted apache (I have to do it when I change anything), didn't work. Updated to r1578, restarted and it worked! Removed brackets, restarted and it still works. I don't get it, nothing changed in backends.py. Why it suddenly started to work? :) Btw. in LDAP se

Re: LDAP authentication changes

2008-11-16 Thread Gavin M. Roy
Try specifically: "(uid=%s)" For the UID mask, without the quotes. The auth does a search to get the full dn and then binds upon that to validate the password. What line is the exception on in reviewboard? On Sun, Nov 16, 2008 at 3:38 PM, Tomas Friml <[EMAIL PROTECTED]>wrote: > > My Base DN is

Re: LDAP authentication changes

2008-11-16 Thread Tomas Friml
My Base DN is: ou=Users,dc=ourdomain,dc=local (note that capital U in Users is correct) UID mask is: uid=%s When I try to run this code manually in python >>> import ldap >>> ldapo = ldap.initialize('ldap://ourldapserver:389') >>> ldapo.search_s('ou=Users,dc=pulse,dc=local', >>> ldap.SCOPE_ONE

Re: LDAP authentication changes

2008-11-16 Thread Gavin M. Roy
Ah yeah, it's in the field setting initial, I don't know how I missed that ;-) On Sun, Nov 16, 2008 at 10:35 AM, Gavin M. Roy <[EMAIL PROTECTED]> wrote: > With the patch I submitted, you set your LDAP Base DN, which would be > something like ou=users,cn=yourdomain,cn=com > and then in the LDAP UI

Re: LDAP authentication changes

2008-11-16 Thread Gavin M. Roy
With the patch I submitted, you set your LDAP Base DN, which would be something like ou=users,cn=yourdomain,cn=com and then in the LDAP UID Mask use something like (uid=%s). I think the DN is still showing up in the UID Mask for a new install, I need to check that out and submit another patch to c

Re: LDAP authentication changes

2008-11-16 Thread Tomas Friml
Hi David, I'm trying to get reviewboard working with our OpenLDAP server but without much success so far. I've tried to use this patch before it was committed and also updated to revision 1573 today. Result is still the same - according to logs I'm getting LDAP error: {'info': 'invalid DN', 'des