ni 2020 07:19
To: ace@ietf.org
Subject: Re: [Ace] "default value" for authz-info endpoint
Hi,
In most cases where I've been involved with implementing a single RFC defined
.well-known URL for actually servicing all end points, it ends up being one
.well-known for default configur
in its well-known information to identify the authz-info endpoint
>> URI it is exposing.
>>
>> @Carsten (or other core experts): Would it make sense to define a new
>> attribute in the /.well-known/core format for Resource Servers using coap?
>>
>> /Ludwig
&g
other core experts): Would it make sense to define a new
> attribute in the /.well-known/core format for Resource Servers using coap?
>
> /Ludwig
>
>
> -Original Message-
> From: Ace On Behalf Of Benjamin Kaduk
> Sent: den 31 maj 2020 00:36
> To: ace@ietf.org
> Sub
@ietf.org
Subject: Re: [Ace] "default value" for authz-info endpoint
On 2020-06-01, at 11:13, Seitz Ludwig wrote:
>
> Hi Ben,
>
> I had a look at the well-known URI list at IANA and it seems that for vanilla
> OAuth 2.0 endpoints (authorization, token, introspect) there a
njamin Kaduk
> Sent: den 31 maj 2020 00:36
> To: ace@ietf.org
> Subject: [Ace] "default value" for authz-info endpoint
>
> Hi all,
>
> I was prompted by the discussion at the interim to look more closely at what
> we say about the "default name" for e
perts): Would it make sense to define a new attribute
in the /.well-known/core format for Resource Servers using coap?
/Ludwig
-Original Message-
From: Ace On Behalf Of Benjamin Kaduk
Sent: den 31 maj 2020 00:36
To: ace@ietf.org
Subject: [Ace] "default value" for authz-info e
Hi all,
I was prompted by the discussion at the interim to look more closely at
what we say about the "default name" for endpoint URIs, e.g., the
authz-info endpoint. The last paragraph of
https://tools.ietf.org/html/draft-ietf-ace-oauth-authz-33#section-5.8.1
says:
The default name of this e
