Loading Profile...
Support in Libraries
I love the discover-on-URL, discover-on-domain, fallback-to-emailtoid path you recommend. Any tips on how to do this with existing libraries (mostly the JanRain libraries).
I’m undecided
1 person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?We're working on libraries to implement the EAUT protocol at http://eaut.googlecode.com/svn/code/. The PHP library should work, and is built on top of the JanRain OpenID library (at least the XRDS stuff).
-
Inappropriate?Python library should work too.
-
Inappropriate?Ok... I was under the impression that emailtoid reccomended flow was:
* Do discovery on the "proper" URL" (ie, http://user@example.com/)
* If that fails, do directed identity on domain (ie, example.com)
* If that fails, use emailtoid
EAUT seems more about some broken way of "mapping" email addresses onto URL patterns...
EMPLOYEE
EMPLOYEE
