oints as this
would be just another one we have to support, monitor and report on
#2 yes, 1 physical endpoint acting as multiple authorization servers
*From:*George Fletcher [mailto:gffle...@aol.com]
*Sent:* Tuesday, August 13, 2013 7:40 AM
*To:* Anthony Nadalin
*Cc:* m...@gluu.org<mailto:m...@g
multiple authorization servers
*From:*George Fletcher [mailto:gffle...@aol.com]
*Sent:* Tuesday, August 13, 2013 7:40 AM
*To:* Anthony Nadalin
*Cc:* m...@gluu.org<mailto:m...@gluu.org>; Justin Richer;
oauth@ietf.org<mailto:oauth@ietf.org>
*Subject:* Re: [OAUTH-WG] OX needs Dynamic Reg
OAuth2 for some use
>>>>>>> cases,
>>>>>>> I'm
>>>>>>> not sure how you abstract the client developer from having to deal with
>>>>>>> them. The client developer is going to be dealing with multiple OAuth2
>&
not sure how you abstract the client developer from having to deal with
>>>>>> them. The client developer is going to be dealing with multiple OAuth2
>>>>>> tokens to multiple endpoints regardless so I don't see another token as
>>>>>> cost
.@aol.com]
*Sent:* Tuesday, August 13, 2013 7:40
AM *To:* Anthony Nadalin *Cc:*
m...@gluu.org; Justin Richer;
oauth@ietf.org *Subject:* Re:
[OAUTH-WG] OX needs D
ess_token. Where is the added client developer complexity?
>>>>>
>>>>> Thanks,
>>>>> George
>>>>>
>>>>>>
>>>>>> Phil
>>>>>>
>>>>>> On 2013-08-13, at 7:48, Justin Richer
Sent: Thursday, August 15, 2013 3:18 PM
To: John Bradley
Cc: m...@gluu.org; oauth@ietf.org
Subject: Re: [OAUTH-WG] OX needs Dynamic Registration: please don't remove!
Agree with John that RFC 6749 is to all intents and purposes final. Also, when
we have a dyn reg spec whose earliest draft
gt;>>> them. The client developer is going to be dealing with multiple OAuth2
>>>>>> tokens to multiple endpoints regardless so I don't see another token as
>>>>>> costly or complex. At a minimum there is the refresh_token and
>>>>>> access_token
2013-08-13, at 7:48, Justin Richer >>>> <mailto:jric...@mitre.org>> wrote:
>>>>>
>>>>>> The spec doesn't care where you deploy at -- if URL space is at a
>>>>>> premium for you, then switch based on input parameters an
trying to
move away from secrets and management of these endpoints as this
would be just another one we have to support, monitor and report on
#2 yes, 1 physical endpoint acting as multiple authorization servers
*From:*George Fletcher [mailto:gffle...@aol.com]
*Sent:* Tuesday, August 13, 2013 7
;>>> OAuth item but it’s growing out of control, we are trying to move away
>>>> from secrets and management of these endpoints as this would be just
>>>> another one we have to support, monitor and report on
>>>> #2 yes, 1 physical endpoint acting as multiple
e-
From:m...@gluu.org <mailto:m...@gluu.org> [mailto:m...@gluu.org]
Sent: Tuesday, August 13, 2013 7:22 AM
To: Anthony Nadalin
Cc: Justin Richer; George Fletcher;oauth@ietf.org <mailto:oauth@ietf.org>
Subject: RE: [OAUTH-WG] OX needs Dynamic Registrat
point acting as multiple authorization servers
>>
>> From: George Fletcher [mailto:gffle...@aol.com]
>> Sent: Tuesday, August 13, 2013 7:40 AM
>> To: Anthony Nadalin
>> Cc: m...@gluu.org; Justin Richer; oauth@ietf.org
>> Subject: Re: [OAUTH-WG] OX needs Dynamic Regist
13 matches
Mail list logo
