A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol Working Group of
the IETF.
Title : Assertion Framework for OAuth 2.0 Client
Authentication and Authorization Grants
Author(s)
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol Working Group of
the IETF.
Title : SAML 2.0 Profile for OAuth 2.0 Client Authentication
and Authorization Grants
Author(s)
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol Working Group of
the IETF.
Title : JSON Web Token (JWT) Profile for OAuth 2.0 Client
Authentication and Authorization Grants
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Web Authorization Protocol Working Group of
the IETF.
Title : OAuth 2.0 Dynamic Client Registration Protocol
Author(s) : Justin Richer
New versions of all three OAuth related assertion documents have been
published. New document titles, URLs and change logs are listed below.
I've tried to address the comments and discuss issues from the IESG review
as well as subsequent discussion and decisions that took place in Orlando.
There
New dynamic registration draft is published. Biggest changes here are
the internationalization/localization capabilities that are now
applicable to human-readable client metadata fields.
-- Justin
On 03/29/2013 04:38 PM, internet-dra...@ietf.org wrote:
A New Internet-Draft is available from
Hi Justin,
I read the latest draft and found endpoints described in the spec returns 403
in no such clients case.
I also read the draft07's editor note below, so I can understand the situation.
[[ Editor's note: If the client doesn't exist,
then the Refresh Access Token shouldn't be valid,
oops sorry, not draft07, but draft06.
On 2013/03/30, at 12:55, nov matake mat...@gmail.com wrote:
Hi Justin,
I read the latest draft and found endpoints described in the spec returns 403
in no such clients case.
I also read the draft07's editor note below, so I can understand the
