Original Message-
> From: Torsten Lodderstedt [mailto:tors...@lodderstedt.net]
> Sent: Monday, July 25, 2011 10:27 AM
> To: Eran Hammer-Lahav
> Cc: OAuth WG
> Subject: Re: [OAUTH-WG] Issue 16, revised Redirection URI section (3.1.2)
>
> Hi Eran,
>
> >> Regarding
Hi Eran,
Regarding this particular section: I think the two different issues (transport
security and endpoint authenticity) should be presented separately.
Which section?
3.1.2.1.
regards,
Torsten.
EHL
___
OAuth mailing list
OAuth@ietf.org
https
> -Original Message-
> From: Torsten Lodderstedt [mailto:tors...@lodderstedt.net]
> Sent: Monday, July 25, 2011 7:19 AM
> To: Eran Hammer-Lahav
> Cc: OAuth WG
> Subject: Re: [OAUTH-WG] Issue 16, revised Redirection URI section (3.1.2)
>
> Hi Eran,
>
> Am
Hi Eran,
Am 25.07.2011 03:28, schrieb Eran Hammer-Lahav:
-Original Message-
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
Of Torsten Lodderstedt
Sent: Wednesday, July 20, 2011 2:15 PM
"The authorization server redirects the user-agent to the
client's redir
> -Original Message-
> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
> Of Torsten Lodderstedt
> Sent: Wednesday, July 20, 2011 2:15 PM
> "The authorization server redirects the user-agent to the
> client's redirection URI previously established with the
>
"The authorization server redirects the user-agent to the
client's redirection URI previously established with the
authorization server during the client registration process."
Conflicts with section 3.1.2.3, which allows to pass a redirect_uri via
URI query parameter.
3.1.2.1 Endpoint C
