OAuth 2.0 Step-up Authentication Challenge Protocol
draft-bertocci-oauth-step-up-authn-challenge-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vittorio Bertocci , Brian Campbell | ||
| Last updated | 2022-03-22 | ||
| Replaced by | draft-ietf-oauth-step-up-authn-challenge | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-oauth-step-up-authn-challenge | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
It is not uncommon for resource servers to require different authentication strengths or freshness according to the characteristics of a request. This document introduces a mechanism for a resource server to signal to a client that the authentication event associated with the access token of the current request doesn't meet its authentication requirements and specify how to meet them. This document also codifies a mechanism for a client to request that an authorization server achieve a specific authentication strength or freshness when processing an authorization request.
Authors
Vittorio Bertocci
Brian Campbell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)