PROPOSAL: RP identifier
Mike Glover
mpg4 at janrain.com
Wed Oct 18 18:19:52 UTC 2006
I'm having trouble envisioning a situation where realm is an insufficient key for authentication purposes. If this isn't for authentication purposes, it absolutely needs to live in an extension. IMO.
-mike
On Wed, 18 Oct 2006 00:06:42 -0700
Dick Hardt <dick at sxip.com> wrote:
> Motivating use cases:
>
> 1) The IdP would like to remember what the user has said a given RP
> can and can't do. The IdP needs a unique identifier for the RP.
> openid.realm is a wild card that could match multiple RPs.
> openid.return_to is a URL that has no guarantee is being used again
> by the same RP.
>
> 2) The RP would like to provide an entry point for the IdP to
> discover more about the RP
>
> 3) Future extensions may want to make calls to the RP
>
> Proposal:
>
> add openid.rp
> set to the URL of the RP
>
> openid.realm needs to match openid.rp
> openid.rp needs to be contained in openid.return_to
>
> openid.rp can take a POST that has openid_identifier=<openid
> identifier>. This is equivalent to the user providing <openid
> identifier> in an OpenID login form
>
> -- Dick
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs
>
>
More information about the specs
mailing list