> I have thought of many solutions to replace ldapdb. I came to
> conclusion than the cleanest, and most useful for the community, would
> be to implement a real db backend forldap. However, I have been told
> that it is an awfully big task !
FYI, I have refactored django-ldapdb so that it is now
nholato
> Sent: Tuesday, March 22, 2011 9:19 AM
> To: django-users@googlegroups.com
> Subject: Re: Implementing a ldap db backend
>
> I have read and tested some more libs.
>
> My concern is that:
>
> django-ldapdb
> (http://opensource.bolloretelecom.eu/projects/djang
users@googlegroups.com [mailto:django-users@googlegroups.com] On
Behalf Of Felipe Prenholato
Sent: Tuesday, March 22, 2011 9:19 AM
To: django-users@googlegroups.com
Subject: Re: Implementing a ldap db backend
I have read and tested some more libs.
My concern is that:
django-ldapdb
I have read and tested some more libs.
My concern is that:
django-ldapdb (http://opensource.bolloretelecom.eu/projects/django-ldapdb/):
amazing idea, I'm working very well to query users, having some issues to
write on LDAP but is more probably due server stuff and not django-ldapdb
itself. Proba
On 03/11/10 07:48, sebastien piquemal wrote:
> I have thought of many solutions to replace ldapdb. I came to
> conclusion than the cleanest, and most useful for the community, would
> be to implement a real db backend for ldap. However, I have been told
> that it is an awfully big task !
>
It wo
Actually I reached a similar position and I'm interested enought to work on
something like that.
You are still interested or have some code to share about it?
Felipe 'chronos' Prenholato.
Linux User nº 405489
Home page: http://chronosbox.org/blog
Twitter: http://twitter.com/chronossc
2010/11/
6 matches
Mail list logo
