es listed. The "audience" and "resource" parameters
may be
used together to indicate multiple target services with a mix of
logical names and locations.
Ciao
Hannes
*From:*Ace <mailto:ace-boun...@ietf.org>
*On Behalf Of * Georg
; On Behalf Of
George Fletcher
Sent: Dienstag, 29. Januar 2019 14:15
To: Ludwig Seitz <mailto:ludwig.se...@ri.se>;
ace@ietf.org<mailto:ace@ietf.org>; oa...@ietf.org<mailto:oa...@ietf.org>
Subject: Re: [Ace] [OAUTH-WG] Shepherd write-up for
draft-ietf-oauth-resource-indicators-01
o indicate multiple target services with a mix of
logical names and locations.
Ciao
Hannes
*From:*Ace *On Behalf Of *George Fletcher
*Sent:* Dienstag, 29. Januar 2019 14:15
*To:* Ludwig Seitz ; ace@ietf.org; oa...@ietf.org
*Subject:* Re: [Ace] [OAUTH-WG] Shepherd write-up for
draft-ietf-oauth-
Hi Ludwig,
the issue is that folks in the OAuth group have defined two parameters, namely
resource (for URIs) and audience (for logical names), and in ACE there is only
one doing both.
To me this appears to be sub-optimal to have different ways to accomplish the
same goal just based on the pro
On 07/02/2019 16:15, Hannes Tschofenig wrote:
Hi Ludwig,
My interpretation of this is that "resource" refers to a single resource
No. Here is the text from token exchange (see last sentence):
resource
[...]
Multiple "resource" parameters may be used to indicate
that the issued t
source" parameters may be
used together to indicate multiple target services with a mix of
logical names and locations.
Ciao
Hannes
From: Ace On Behalf Of George Fletcher
Sent: Dienstag, 29. Januar 2019 14:15
To: Ludwig Seitz ; ace@ietf.org; oa...@ietf.org
Subject: Re: [Ace] [OAUTH-W
Hi Ludwig,
> My interpretation of this is that "resource" refers to a single resource
No. Here is the text from token exchange (see last sentence):
resource
OPTIONAL. Indicates the location of the target service or
resource where the client intends to use the requested security
Thank you so much for the background!
I believe that since the latest draft of the resource indicators spec
[1] allows for abstract identifiers, and since a URN is also a URI, you
could easily use a URN syntax to accomplish the use case outlined in
your email.
resource=urn:x-mydevices:temper
On 28/01/2019 23:12, George Fletcher wrote:
I also don't know that this raises to the level of "concern" but I find
the parameter name of "req_aud" odd. Given that the parameter in the
resource-indicators spec is 'resource' why not use a parameter name of
'audience'. That said, I have not read
[added ace@ietf.org kinda per suggestion from Mike]
I don't know that there are concerns about “req_aud” per se.. Admittedly, I
did use the word "concerns" but I was more trying to say that referencing
it from the draft-ietf-oauth-resource-indicators document wasn't needed to
address Vittorio's r
10 matches
Mail list logo