Damjan wrote: >> SqlAlchemy is not requirement for OpenID but you still need SQL backend >> for OpenID. I believe that's only limitation of python-openid library >> which might be already addressed and I am not aware about it. My >> implementation works properly with MySQL only. I know how to fix SQLite >> backend but had no time for that yet. I have not tested it with >> PostgreSQL as well (but I hope it works). >> > > I don't see why an OpenID library or middleware would need to have any > storage ... can't it just give me the ID of the user, and I could > store it in my session or do whatever I choose to do with it!?? > That's because how OpenID works. OpenID workflow is following (I hope :-) ): 1) User connects to your server and says what is his/her OpenID; 2) Your server should remember somehow who and when initiated OpenID request. So it create OpenID session and saves it to database (OpenID session usually is encoded into return URL); 3) Your server redirects user to OpenID server where user performs login, allow and other required actions; 4) OpenID server returns user to your server (to return URL) and here your server should know somehow that it is the same user that has initiated OpenID login.
I hope that it clarifies why it can't just give you ID of the user. Regards, Dalius --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
