⌕ Поиск по атласу

IETF · RFC · RFC9470

RFC9470 · OAuth 2.0 Step Up Authentication Challenge Protocol

OAuth 2.0 Step Up Authentication Challenge Protocol

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.

Официальная английская аннотация

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.

Связи документа

Официальный источник · 2023-09-01

Полные импортированные сведения карточки
{
  "id": "RFC9470",
  "number": 9470,
  "title_en": "OAuth 2.0 Step Up Authentication Challenge Protocol",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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.",
  "authors": [
    "V. Bertocci",
    "B. Campbell"
  ],
  "organizations": [],
  "publication_date": "2023-09-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "oauth",
  "source_draft": "draft-ietf-oauth-step-up-authn-challenge-17",
  "page_count": 14,
  "doi": "10.17487/RFC9470",
  "keywords": [
    "security",
    "oauth2",
    "openid connect",
    "oauth",
    "step-up"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9470/",
    "html": "https://www.rfc-editor.org/rfc/rfc9470.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9470.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9470/"
  }
}