<HTML dir=ltr><HEAD></HEAD>
<BODY>
<DIV id=idOWAReplyText6902 dir=ltr>
<DIV dir=ltr>See a previous offer. There is no critical reason to use proprietary APIs.- at least for openid CCA/SSO.</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>If you have a technical control over a domain name and are willing to subscribe to Google Apps premium for a month (before you cancel the subscription, else pay $50 pa), for 2.5 months I'll help add an openid login to it -- one that (hopefully) anyone can use, with any reasonably conforming OP.</DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>There are several parties now running outsourced IDPs, to Google Apps RP sites. I happened to do with an OpenID IDP/OP.<BR></DIV>
<DIV dir=ltr>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr><FONT face=Tahoma size=2><B>From:</B> Martin Paljak<BR><B>Sent:</B> Fri 4/11/2008 1:44 AM<BR><B>To:</B> OpenID General<BR><B>Cc:</B> discuss OpenID libraries and development<BR><B>Subject:</B> [OpenID] Google App Engine & python-openid<BR></FONT><BR></DIV></DIV>
<DIV><PRE style="WORD-WRAP: break-word">Hi all.
Google App Engine definitely seems like a nice thing to play with when
creating 'cool yet small' 'next big things' but it has one limitation:
it is Google specific and the User API talks about Google accounts and
e-mail addresses, no OpenID whatsoever.
Does python-openid support GAE / does GAE support python-openid?
Reading the web leaves me thinking that a special url loader for
python-openid is needed as well as custom DB backend.
Anyone working on this or has more insight - I'd love to hear about it.
Thanks,
Martin
_______________________________________________
general mailing list
general@openid.net
http://openid.net/mailman/listinfo/general
</PRE></DIV></BODY></HTML>