RFC8252 · OAuth 2.0 for Native Apps

{
  "id": "RFC8252",
  "number": 8252,
  "title_en": "OAuth 2.0 for Native Apps",
  "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": "OAuth 2.0 authorization requests from native apps should only be made through external user-agents, primarily the user's browser. This specification details the security and usability reasons why this is the case and how native apps and authorization servers can implement this best practice.",
  "authors": [
    "W. Denniss",
    "J. Bradley"
  ],
  "organizations": [],
  "publication_date": "2017-10-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "oauth",
  "source_draft": "draft-ietf-oauth-native-apps-12",
  "page_count": 21,
  "doi": "10.17487/RFC8252",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC6749"
    ],
    "updated_by": [],
    "is_also": [
      "BCP212"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8252/",
    "html": "https://www.rfc-editor.org/rfc/rfc8252.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8252.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8252/"
  }
}