Jared, > It seems weird to return the user's OpenID identifier, when ultimately > the OP Endpoint URL is what you need if you want to authenticate the > user. However, I think "http://specs.openid.net/auth/2.0/server"; > should have been used for the rel type, as it is actually defined by > OpenID Authentication 2.0 spec for that purpose.
I don't think it's weird at all to use webfinger to return one's OpenID identifier. After all, Webfinger is intended to be a means of discovering information about a person. Once the identifier is learned, then the OP can be discovered based on that ID. Returning the OP URL without the user's identifier is not as useful, since the OP would not know who is being authenticated: it would then have to prompt the user for his identity. > What is really needed is an agreed upon URI for what was the "http:// > specs.openid.net/auth/2.0/signon" type (which carried the user's > OpenID URL in XRDS' LocalID element (which is gone from XRD)). If the rel value is "http://openid.net/identity"; and the href value represents the user's OpenID identifier, then the RP knows what to do with that. I really think that's what we should try to agree upon. This would minimize the additional effort an RP would have to make, just adding a Webfinger resolution step and making no changes to the OpenID spec. The RP might want to implement Webfinger, anyway, in order to discover information about the user, such as his name, picture, or other information he wants to share with the world. Paul _______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
