continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Zhao" <>
Subject RE: Suggestions on implemeting the Continuum User Authentication via LDAP
Date Wed, 19 Oct 2005 21:32:37 GMT

Getting the userid and password is good enough.

Getting the user group info. from LDAP is nice since that can save some of the work of assigning
users to groups manually. However, that may make the Continuum depends on LDAP too much: any
changes to the user group have to go through LDAP. Therefore I prefer using LDAP only for



-----Original Message-----
From: Emmanuel Venisse []
Sent: Wed 10/19/2005 8:39 AM
Subject: Re: Suggestions on implemeting the Continuum User Authentication via LDAP
With the actual code, you can't do it. Continuum code need a little refactoring for 
support other user management implementation

- create a user management api project
- create a user management store project that use only database for 
authentication/add/delete/search user
- create a user management ldap project with ldap access and database access

Which informations do you want to use from ldap? only user/password?


Frank Zhao a écrit :
> Since we need this feature pretty soon, I am planning to make a patch for the LDAP feature
in Continuum. Any suggestions/hints on how to design/implement this feature will be highly
> In addition, how long do you think it takes for the implementation? This would be very
helpful for me to evaluate the work.
> Thanks!
> Frank
> -----Original Message-----
> From: Brett Porter []
> Sent: Mon 10/17/2005 9:35 PM
> To:
> Subject: Re: Continuum User Authentication via LDAP
> I would like to see that happen. Please file it as a feature request
> and we will consider it for future versions.
> - Brett
> On 10/17/05, Frank Zhao <> wrote:
>>I am very glad to see the recent Continuum Beta 1 version having user management functions.
It is very important to us.
>>My question is will Continuum support LDAP for the user authentication? If not, is
there a plan to do that in the near future?
>>Thanks in advance,

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message