confusion.
>>
>> Thanks for reading the draft, Torsten.
>>
>> -- Mike
>>
>> From: Torsten Lodderstedt [mailto:tors...@lodderstedt.net]
>> Sent: Sunday, November 13, 2016 2:32 PM
>> To: Mike
* Re: [OAUTH-WG] Comments on
draft-jones-oauth-resource-metadata-00
Hi Mike,
just read your spec and I'm also a bit confused about the "resource"
meta data element in section 2.
I would assume the metadata are provided for a certain resource server
managing a set of resources in a pa
: Re: [OAUTH-WG] Comments on draft-jones-oauth-resource-metadata-00
Hi Mike,
just read your spec and I'm also a bit confused about the "resource" meta data
element in section 2.
I would assume the metadata are provided for a certain resource server managing
a set of resources in
Hi Mike,
just read your spec and I'm also a bit confused about the "resource"
meta data element in section 2.
I would assume the metadata are provided for a certain resource server
managing a set of resources in a particular administrative domain. So I
would prefer to name the respective ele
Mike, thanks for drafting and publishing these specifications. I have a
couple of questions regarding the draft-jones-oauth-resource-metadata-00.
1. Is a "protected resource" a server? or an actual API endpoint. The
non-normative examples use /.well-known/oauth-protected-resource and
/resource
