All,
Based on the feedback during the meeting in Montreal and on the mailing
list, we think that the WG has decided to adopt this draft.
*Authors,*
Feel free to submit a new WG -00 draft.
We would like to point out that Tony has raised some security concerns
about this, so please take that into
+1
Hans.
On Sat, Jul 21, 2018 at 7:12 PM, Filip Skokan wrote:
> I support the adoption or this document by the WG.
>
> Filip Skokan
>
> Odesláno z iPhonu
>
> 19. 7. 2018 v 19:43, Rifaat Shekh-Yusef :
>
> Hi all,
>
> This is the call for adoption of the 'JWT Response for OAuth Token
> Introspect
I support the adoption or this document by the WG.
Filip Skokan
Odesláno z iPhonu
19. 7. 2018 v 19:43, Rifaat Shekh-Yusef :
> Hi all,
>
> This is the call for adoption of the 'JWT Response for OAuth Token
> Introspection' document following the presentation by Torsten at the Montreal
> IETF
Hi Mark,
> Am 20.07.2018 um 17:47 schrieb Mark Dobrinic :
>
> I +1 this,
thanks
>
> but at the same time, I'm wondering what happened with the argument that
> this should be solved by Token Exchange instead of Introspect?
We presented two use case in London, (1) providing evidence for the RS’s
I +1 this,
but at the same time, I'm wondering what happened with the argument that
this should be solved by Token Exchange instead of Introspect?
Cheers!
Mark
On 20/07/18 17:39, Phil Hunt wrote:
> +1 adoption
>
> I have always been concerned about clients doing introspection. Use of
> jwt he
+1 adoption
I have always been concerned about clients doing introspection. Use of jwt
helps because responses further restricted rather than less (jwe).
Phil
> On Jul 20, 2018, at 7:25 AM, Rob Otto
> wrote:
>
> I support this as well
>
>> On Fri, 20 Jul 2018 at 15:22, Brian Campbell
>>
I support this as well
On Fri, 20 Jul 2018 at 15:22, Brian Campbell wrote:
> +1
>
> On Thu, Jul 19, 2018 at 1:51 PM, William Denniss <
> wdenniss=40google@dmarc.ietf.org> wrote:
>
>> I support adoption of this document by the working group.
>>
>>
>> On Thu, Jul 19, 2018 at 10:43 AM, Rifaat S
+1
On Thu, Jul 19, 2018 at 1:51 PM, William Denniss <
wdenniss=40google@dmarc.ietf.org> wrote:
> I support adoption of this document by the working group.
>
>
> On Thu, Jul 19, 2018 at 10:43 AM, Rifaat Shekh-Yusef <
> rifaat.i...@gmail.com> wrote:
>
>> Hi all,
>>
>> This is the call for adopt
h
> Subject: [OAUTH-WG] Call for adoption of "JWT Response for OAuth Token
> Introspection"
>
> Hi all,
>
> This is the call for adoption of the 'JWT Response for OAuth Token
> Introspection' document following the presentation by Torsten at the Montre
Shekh-Yusef; oauth
Subject: Re: [OAUTH-WG] Call for adoption of "JWT Response for OAuth Token
Introspection"
I’m concerned over the security implications of a client being able to
introspect a token, for bearer tokens this can be very problematic, so unless
the issues with possible token
: Thursday, July 19, 2018 10:44 AM
To: oauth
Subject: [OAUTH-WG] Call for adoption of "JWT Response for OAuth Token
Introspection"
Hi all,
This is the call for adoption of the 'JWT Response for OAuth Token
Introspection' document following the presentation by Torsten at the Mo
Hi all,
This is the call for adoption of the 'JWT Response for OAuth Token
Introspection' document following the presentation by Torsten at the
Montreal IETF meeting where we didn't have a chance to do a call for
adoption in the meeting itself.
Here is presentation by Torsten:
https://datatracker
12 matches
Mail list logo
