Here is a quick update on my IdentityProvider progress -- since Sergio 
no longer immediately needs the CASIdentityProvider I started work on an 
LdapIdentityProvider this weekend.  LDAP authentication is a little more 
conventional compared to CAS, so I thought it would be a better place to 
jump in and learn.  It is starting to take shape, but I have some rough 
edges to smooth out before releasing the code into the wild.

I think that the LdapIdentityProvider will be a great resource for 
people in corporate environments since most businesses big enough to 
write internal applications have all of their users stored in a 
directory of some sort (Active Directory, Sun One, OpenLDAP, etc).

The idea is to authenticate users against an LDAP directory and to pull 
most of their basic user information (name, email, phone number and 
more) from the directory as well.  There is still a tg_user table in the 
database but it only contains an id and a username.  The table's primary 
purpose is to provide referential integrity against the visit records 
and other business objects.

I'd enjoy hearing any comments or criticism about the idea.

Thanks,

Tim



Timothy Freund wrote:
> Jeff Watkins wrote:
>  > Actually the best way to implement this would be to write a
>  > CasIdentityProvider class and use that instead of
>  > SqlObjectIdentityProvider. Ultimately, it is the IdentityProvider
>  > classes that are responsible for determining who the request is from.
> 
> 
> Thanks for pointing me in the right direction -- I will be able to 
> really dig in and get that working over this weekend.
> 
> Tim
> 
> 
> 


-- 
Timothy Freund
http://digital-achievement.com
http://edodyssey.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to