Brian Campbell
Sent: Monday, April 23, 2018 1:45 PM
To: George Fletcher
Cc: oauth
Subject: Re: [OAUTH-WG] scp claim in draft-ietf-oauth-token-exchange-12
draft -13 was just published with these changes
On Mon, Apr 23, 2018 at 2:15 PM, George Fletcher
mailto:gffle...@aol.com>> wrote:
+1
On
-- Mike
>>
>>
>>
>> *From:* OAuth *On Behalf Of * Brian Campbell
>> *Sent:* Wednesday, April 18, 2018 8:17 AM
>> *To:* Torsten Lodderstedt
>> *Cc:* oauth
>> *Subject:* Re: [OAUTH-WG] scp claim in draft-ietf-oauth-token-exchange-12
iven it makes the OAuth suite of specs
more self-consistent.
-- Mike
*From:* OAuth mailto:oauth-boun...@ietf.org>> *On Behalf Of * Brian Campbell
*Sent:* Wednesday, April 18, 2018 8:17 AM
*To:* Torsten Lodderstedt mailto:tors...@lodderstedt.net>>
*Cc:* oauth mailto:oauth
+1
From: Brian Campbell
Sent: Monday, April 23, 2018 12:13 PM
To: Torsten Lodderstedt
Cc: Mike Jones ; oauth
Subject: Re: [OAUTH-WG] scp claim in draft-ietf-oauth-token-exchange-12
I just noticed/remembered that the draft also currently defines a "cid" claim
for the client identi
-- Mike
>
>
>
> *From:* OAuth *On Behalf Of * Brian Campbell
> *Sent:* Wednesday, April 18, 2018 8:17 AM
> *To:* Torsten Lodderstedt
> *Cc:* oauth
> *Subject:* Re: [OAUTH-WG] scp claim in draft-ietf-oauth-token-exchange-12
>
>
&g
Behalf Of Brian Campbell
> Sent: Wednesday, April 18, 2018 8:17 AM
> To: Torsten Lodderstedt
> Cc: oauth
> Subject: Re: [OAUTH-WG] scp claim in draft-ietf-oauth-token-exchange-12
>
> The draft-ietf-oauth-token-exchange document makes use of scope and at some
> point in
claim in draft-ietf-oauth-token-exchange-12
The draft-ietf-oauth-token-exchange document makes use of scope and at some
point in that work it came to light that, despite the concept of scope being
used lots of places elsewhere, there was no officially registered JWT claim for
scope. As a result
The draft-ietf-oauth-token-exchange document makes use of scope and at some
point in that work it came to light that, despite the concept of scope
being used lots of places elsewhere, there was no officially registered JWT
claim for scope. As a result, we (the WG) decided to have
draft-ietf-oauth-t
Hi all,
I I’m wondering why draft-ietf-oauth-token-exchange-12 defines a claim „scp“ to
carry scope values while RFC 7591 and RFC 7662 use a claim „scope“ for the same
purpose. As far as I understand the text, the intension is to represent a list
of RFC6749 scopes. Is this correct? What’s the r
