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.

On 23 Feb, 2006, at 10:19 pm, Timothy Freund wrote:

It looks like we could add CAS support to Identity just by implementing 

a method called identity_from_cas in turbogears.identity.visitor


--
Jeff Watkins

Getting an education was a bit like a communicable sexual disease. It made you unsuitable for a lot of jobs and then you had the urge to pass it on. 
-- (Terry Pratchett, Hogfather)



--~--~---------~--~----~------------~-------~--~----~
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