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

IETF · RFC · RFC7591

RFC7591 · OAuth 2.0 Dynamic Client Registration Protocol

OAuth 2.0 Dynamic Client Registration Protocol

This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.

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

This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7591",
  "number": 7591,
  "title_en": "OAuth 2.0 Dynamic Client Registration 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": "This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.",
  "authors": [
    "J. Richer",
    "M. Jones",
    "J. Bradley",
    "M. Machulak",
    "P. Hunt"
  ],
  "organizations": [],
  "publication_date": "2015-07-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-dyn-reg-30",
  "page_count": 39,
  "doi": "10.17487/RFC7591",
  "keywords": [
    "OpenID Connect Dynamic Client Registration",
    "OpenID Connect",
    "oidc",
    "openid",
    "user managed access",
    "uma",
    "Dynamic Registration",
    "Dynamic Client Registration"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7591/",
    "html": "https://www.rfc-editor.org/rfc/rfc7591.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7591.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7591/"
  }
}