Actually, the more I look at it I don't even know if you need to mess with a new identity provider at all. Here are the steps that I think will work:
1. Change your login method so that it always posts to an openid-initialization method. (make sure to set "identity.failure_url" in your config to point to this method) 2. From that initialization method, start the login process and send the user to the openid server, directing it to go back to a third controller method. 3. Have the third controller method finish the openid verification process and log the user in directly. To log someone in directly, look up their object in the database and use it as the sole parameter to turbogears.identity.set_current_identity() This is all written around the idea of hijacking the sqlobject or sqlalchemy providers and handling logins manually. I put some of the code I was working on up on svn, but I was sick at the time and really was not thinking well. If it will help at all you can find it at: http://recursivethought.googlecode.com/svn/oididentity/trunk When I get some time to work on this and test it I will finish this up and release it as a plugin. -Adam --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
