I spoke abit to Therry about it and shared with him my far from
working code. If it is worth anything I will let you know what I
believe would be helpful. Ldap authentication itself is actually kind
of trivial. Like almost anything else there is a establish connection
portion, a query portion and
User admin created with the password you specified."
114 print "\n\n"
115 print "*"*70
116 print "\n"
117 if secure:
118 print "Login to the SAGE notebook as admin with the password you
specified above."
119 #nb.del_user('root')
On Jul 18, 3
tweak I make breaks something else. Perhaps if
I knew how it was all connected a small patch would be possible. I
don't, and
trial and error is very inefficient.
On Jul 21, 12:30 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 20, 2008 at 11:01 PM, Michael_
to
check instead
of the ldap. More properly the caching mechanism should be at least
hashing and
probably pushed into authenticate_uid.
-michael
On Jul 18, 8:23 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 18, 2008 at 2:17 AM, Michael_D_G <[EMAIL PROTECT
I am in the processes of implementing ldap authentication as well...
although it is not going so smoothly.
I was trying to override the classes in user_db.py with some custom
classes.
Fine. That seems ok. The UserDatabase
is used throughout twist.py which seemed to be the server software.
avatars.
