{
  "draft": "draft-ietf-oauth-step-up-authn-challenge-17",
  "doc_id": "RFC9470",
  "title": "OAuth 2.0 Step Up Authentication Challenge Protocol",
  "authors": [
    "V. Bertocci",
    "B. Campbell"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "14",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Web Authorization Protocol",
  "abstract": "It is not uncommon for resource servers to require different authentication strengths or recentness according to the characteristics of a request.  This document introduces a mechanism that resource servers can use to signal to a client that the authentication event associated with the access token of the current request does not meet its authentication requirements and, further, 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 recentness when processing an authorization request.",
  "pub_date": "September 2023",
  "keywords": [
    "security",
    "oauth2",
    "openid connect",
    "oauth",
    "step-up"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9470",
  "errata_url": "https://www.rfc-editor.org/errata/rfc9470"
}