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

IETF · RFC · RFC8628

RFC8628 · OAuth 2.0 Device Authorization Grant

OAuth 2.0 Device Authorization Grant

The OAuth 2.0 device authorization grant is designed for Internet- connected devices that either lack a browser to perform a user-agent- based authorization or are input constrained to the extent that requiring the user to input text in order to authenticate during the authorization flow is impractical. It enables OAuth clients on such devices (like smart TVs, media consoles, digital picture frames, and printers) to obtain user authorization to access protected resources by using a user agent on a separate device.

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

The OAuth 2.0 device authorization grant is designed for Internet- connected devices that either lack a browser to perform a user-agent- based authorization or are input constrained to the extent that requiring the user to input text in order to authenticate during the authorization flow is impractical. It enables OAuth clients on such devices (like smart TVs, media consoles, digital picture frames, and printers) to obtain user authorization to access protected resources by using a user agent on a separate device.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8628",
  "number": 8628,
  "title_en": "OAuth 2.0 Device Authorization Grant",
  "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": "The OAuth 2.0 device authorization grant is designed for Internet- connected devices that either lack a browser to perform a user-agent- based authorization or are input constrained to the extent that requiring the user to input text in order to authenticate during the authorization flow is impractical. It enables OAuth clients on such devices (like smart TVs, media consoles, digital picture frames, and printers) to obtain user authorization to access protected resources by using a user agent on a separate device.",
  "authors": [
    "W. Denniss",
    "J. Bradley",
    "M. Jones",
    "H. Tschofenig"
  ],
  "organizations": [],
  "publication_date": "2019-08-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-device-flow-15",
  "page_count": 21,
  "doi": "10.17487/RFC8628",
  "keywords": [
    "Security Area",
    "OAuth",
    "Security",
    "Authorization",
    "Smart Objects",
    "IoT",
    "Internet of Things",
    "Internet of Things Security",
    "OAuth for Constrained Devices",
    "OAuth IoT Security"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8628/",
    "html": "https://www.rfc-editor.org/rfc/rfc8628.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8628.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8628/"
  }
}