ssion for the creation and stewardship of
>> JWT.
>>
>> -- Mike
>>
>> -Original Message-
>> From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of John Bradley
>> Sent: Wednesday, January 20, 2016 12:44 PM
>>
OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Tuesday, January 19, 2016 3:48 AM
To: oauth@ietf.org
Subject: [OAUTH-WG] Call for Adoption: Authentication Method Reference Values
Hi all,
this is the call for adoption of Authentication Method Reference Values, see
Right but OAuth is the layer that needs to relay the request to the authen
service.
+1 on adoption
However we need to discuss more on w this as a registry or how it is used in
the overall architecture to pass signalling (hint maybe that falls to connect?)
Phil
> On Jan 20, 2016, at 12:37, J
the "amr" claim, which is registered in the
>> OAuth-established registry at http://www.iana.org/assignments/jwt, is
>> squarely within the OAuth WG's mission for the creation and stewardship of
>> JWT.
>>
>> -- Mike
&
ietf.org] On Behalf Of John Bradley
> Sent: Wednesday, January 20, 2016 12:44 PM
> To: Justin Richer
> Cc:
> Subject: Re: [OAUTH-WG] Call for Adoption: Authentication Method Reference
> Values
>
> I see your point that it is a fine line reporting how a person authenticated
Justin Richer
Cc:
Subject: Re: [OAUTH-WG] Call for Adoption: Authentication Method Reference
Values
I see your point that it is a fine line reporting how a person authenticated to
a Authorization endpoit (it might be by SAML etc) and encouraging people to use
OAuth for Authentication.
We a
I see your point that it is a fine line reporting how a person authenticated to
a Authorization endpoit (it might be by SAML etc) and encouraging people to use
OAuth for Authentication.
We already have the amr response in connect. The only thing really missing is
a registry. Unless this is a
Just reiterating my stance that this document detailing user authentication
methods has no place in the OAuth working group.
— Justin
> On Jan 19, 2016, at 6:48 AM, Hannes Tschofenig
> wrote:
>
> Hi all,
>
> this is the call for adoption of Authentication Method Reference Values, see
> http
. Each of the other 7 amr
> values are "specified" in a few lines with a reference (or two). A "First
> Come First Served" basis is probably sufficient, with the "specification"
> just the description in the registry (that can include references).
>
>
in a few lines with a reference (or two). A "First
> Come First Served" basis is probably sufficient, with the "specification"
> just the description in the registry (that can include references).
>
I agree, "Specification Required" does seem like a high bar.
&
wo). A "First Come
First Served" basis is probably sufficient, with the "specification" just the
description in the registry (that can include references).
--
James Manger
-----Original Message-----
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
Sent
Hi all,
this is the call for adoption of Authentication Method Reference Values, see
https://tools.ietf.org/html/draft-jones-oauth-amr-values-03
Please let us know by Feb 2nd whether you accept / object to the
adoption of this document as a starting point for work in the OAuth
working group.
Not
12 matches
Mail list logo
