susundberg / django-auth-ldap-ad Goto Github PK

I'm using a copy of your project in many projects I build, and you have done a great job !
This package is really awesome... and easy to use !

Do you project to put it into pypi ? We could install it directly :
$ pip install django-auth-ldap-ad
This would be amazing...

Thanks !

First, sorry for filing an issue for this, but I could not find another way of contacting you. I would like to add functionality to this module to be able to look up user information (first_name, email, etc.) for arbitrary users, not just the currently logged in user.

I think what needs to be done is implementing an LDAPSearch class. I would just like to know before I try to look into this: would you want something like this in such a lightweight module? And: What source should I be looking at for the official protocol for implementing such a search?

I would like cac/pki certification with my django app.

Any suggestions or pointers?

I found this but they just said:
"I just did this today by subclassing django.contrib.auth.middleware.RemoteUserMiddleware and changed the header property to the one I had set in my apache conf. I just added the django.contrib.auth.backends.RemoteUserBackend and my middleware to the settings and it works perfectly."

seems this might be similar to ldap authentication as well?

I really don't know much about cac/pki except that I am tired of logging in through username/password...

even if it's only one URI. The default value and README.md are not so clear about this. If in settings.py I use:

'ldap://myserver'

instead of:

['ldap://myserver']

I get LDAPError 2, 'No such file or directory' and 34, 'Numerical result out of range'.

Just wanted to say, I found the "Why" section of your README very useful. Everybody should do it!

In this case it really helped answer the first question that popped into my head, "why wouldn't I use the other more mature one".

This is more a result of investigation than feature request. At this point ldap3 supports both Python2 and Python3 so I'm proposing following migration plan (and am hoping to be able to further it myself)

1. Migrate from ldap-python to ldap3 without caring about Python3 compat
2. Add test harness for Python3
3. Fix test and code until everything passes with both Python2 and Python3
   I'm proposing minimum requirements to be set to later builds of 2.7 and 3.3 branches as sensible since syntax overlap is significant