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
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);
I can remember that in the http session (which could be Beakers secure
cookie)
On 7/19/09 8:57 PM, Dalius Dobravolskas wrote:
Damjan wrote:
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);
I can remember that in the http session (which
On 7/19/09 10:08 PM, Damjan wrote:
I guess that's not the most secure thing to do but if you want you could
try to write your own OpenID implementation. It might be possible that I
have oversimplified everything and there are more steps to make OpenID
secure. I really doubt that OpenID
This is exactly the reason I would use django for my next big project.
Much better openid support, like with django-clickpass. I hear
repoze.what is making progress with .who but I believe the user base
is still pretty small.
Cheers,
Tom Longson (nym)
--
Nicholl William wrote:
Hi All,
I am planing to use openid authentication for my web site.My site back
end with MongoDB and not using SQLAlchemy. So probably i need to
customize authentication session for database access.
I know Authkit has openid support and also repoze.who has openid
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
