Murray Kucherawy has entered the following ballot position for
draft-ietf-oauth-rar-19: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
ht
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol WG of the IETF.
Title : OAuth 2.0 Rich Authorization Requests
Authors : Torsten Lodderstedt
Just
Hi Murray,
thanks for you review.
I updated the draft based on it and submitted -20
Here is the diff
https://author-tools.ietf.org/iddiff?difftype=--hwdiff&url2=draft-ietf-oauth-rar-20.txt
> Am 15.12.2022 um 09:34 schrieb Murray Kucherawy via Datatracker
> :
>
> Murray Kucherawy has entere
Éric Vyncke has entered the following ballot position for
draft-ietf-oauth-rar-20: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
https:/
Robert Wilton has entered the following ballot position for
draft-ietf-oauth-rar-20: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
https
Hi Tobias,
OAuth 2.0 and OIDC originally have a model where the client metadata is
made to match the server's requirements and supported algorithms.
This looks roughly like this:
* The server has its metadata published at the well-known URL.
* The client developer examines the server met
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol WG of the IETF.
Title : OAuth 2.0 Rich Authorization Requests
Authors : Torsten Lodderstedt
Just
Hi Eric,
> Am 15.12.2022 um 11:33 schrieb Éric Vyncke via Datatracker :
>
> Éric Vyncke has entered the following ballot position for
> draft-ietf-oauth-rar-20: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC line
Hi Robert,
Thanks for your review.
> Am 15.12.2022 um 11:37 schrieb Robert Wilton via Datatracker
> :
>
> Robert Wilton has entered the following ballot position for
> draft-ietf-oauth-rar-20: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addr
On Thu, Dec 15, 2022 at 12:39 PM Tobias Looker
wrote:
> > Would be good to see tos_uri and policy_uri (personally, I'm
> disappointed in the name policy_uri as policy is a much broader context
> than privacy -- but that discussion is over =)
>
> Ok so to be clear you are suggesting we update the
Hi Vladimir,
> OAuth 2.0 and OIDC originally have a model where the client metadata is made
> to match the server's requirements and supported algorithms.
Agreed.
> For a client to publish metadata tailored to one particular OP / AS server
> doesn't appear to be much of a problem. How do you
> Don't you think the AS should state what it requires in a client discovery
> call as well?
I guess I'm trying to understand what exactly this would be and where one would
draw the line, for example would the AS simply publish a list of required
client metadata properties OR a list of metadata
12 matches
Mail list logo
