[Openid-specs-ab] Inconsistency in redirect_uri definitions

[Justin Richer]

+1 to the proposed fix -- greater specificity seems to be the intent here.

  -- Justin

On 06/07/2013 01:33 PM, Mike Jones wrote:
>
> While working on the spelling and grammar check, I noticed the 
> following in redirect_uri definitions. While I hate to bring this up 
> while we're trying to finish the Implementer's Drafts, this is 
> potentially a recall-class issue, so I wanted to raise it now, rather 
> than have it come up later.
>
> Messages, Basic, and Implicit say:
>
> redirect_uri
>
> REQUIRED. Redirection URI to which the response will be sent. This 
> MUST be pre-registered with the OpenID Provider.
>
> Standard says:
>
> redirect_uri
>
> REQUIRED. Redirection URI to which the response will be sent. The 
> Scheme, Host, Path, and Query Parameter segments of this URI MUST 
> match one of the redirect_urisregistered for the client_idin the 
> OpenID Connect Dynamic Client Registration 1.0 
> <file:///C:%5Cmbj%5CDSG%5COpenID%5Copenid-connect-standard-1_0.html#OpenID.Registration> 
> [OpenID.Registration] specification.
>
> Dynamic Registration says:
>
> redirect_uris
>
> REQUIRED. Array of redirection URIs values used in the Authorization 
> Code and Implicit grant types. One of these registered redirection URI 
> values MUST match the Scheme, Host, and Path segments of the 
> redirect_uriparameter value used in each Authorization Request.
>
> Should Messages, Basic, and Implicit be changed to match Standard?  
> That's my sense of the situation, but wanted to get others' input 
> before doing so.
>
> Thanks,
>
> -- Mike
>
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130607/0b26945a/attachment.html>