Hello Dave,
>
> I agree that the best deployment option is: 1 brand = 1 issuer = 1
> discovery doc, however that is not always possible.
>
> I'd like to understand Francis what particular issue you see from allowing
> an AS to specify multiple authorization_endpoints?
>
Confusing End User! A user
Hi Benjamin,
My responses are between the lines.
Hi Denis,
On Tue, Jun 02, 2020 at 10:20:36AM +0200, Denis wrote:
Hi Benjamin,
Responses are between the lines.
On Fri, May 22, 2020 at 11:37:28AM +0200, Denis wrote:
Hi Benjamin,
On Thu, May 14, 2020 at 04:29:43PM +0200, Denis wrote:
Sinc
Thank you for the replies to this message.
I agree that the best deployment option is: 1 brand = 1 issuer = 1
discovery doc, however that is not always possible.
I'd like to understand Francis what particular issue you see from allowing
an AS to specify multiple authorization_endpoints?
I can see
Hi Hannes,
First of all, I do appreciate your efforts to attempt to get rid of the
"MUST NOT" in the "Privacy considerations" section.
Let us look at the following proposed sentence:
While this is technical possible, it is important to note that the OAuth
2.0 protocol does not aim to expose
We(Yahoo! JAPAN) agree with option 2.
Option 1 is not realistic for us as an IdP with thousands of clients because it
will force them to change implementations.
Also, we already implemented 2 and it was not complicated.
Kazuki Tsuzuku
> On 30 May 2020, at 08:58, Daniel Fett wrote:
>
> Hi all,
