RFC8292 · Voluntary Application Server Identification (VAPID) for Web Push
Voluntary Application Server Identification (VAPID) for Web Push
An application server can use the Voluntary Application Server Identification (VAPID) method described in this document to voluntarily identify itself to a push service. The "vapid" authentication scheme allows a client to include its identity in a signed token with requests that it makes. The signature can be used by the push service to attribute requests that are made by the same application server to a single entity. The identification information can allow the operator of a push service to contact the operator of the application server. The signature can be used to restrict the use of a push message subscription to a single application server.
IETF · RFCОфициальная английская аннотация
An application server can use the Voluntary Application Server Identification (VAPID) method described in this document to voluntarily identify itself to a push service. The "vapid" authentication scheme allows a client to include its identity in a signed token with requests that it makes. The signature can be used by the push service to attribute requests that are made by the same application server to a single entity. The identification information can allow the operator of a push service to contact the operator of the application server. The signature can be used to restrict the use of a push message subscription to a single application server.
{
"id": "RFC8292",
"number": 8292,
"title_en": "Voluntary Application Server Identification (VAPID) for Web Push",
"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": "An application server can use the Voluntary Application Server Identification (VAPID) method described in this document to voluntarily identify itself to a push service. The \"vapid\" authentication scheme allows a client to include its identity in a signed token with requests that it makes. The signature can be used by the push service to attribute requests that are made by the same application server to a single entity. The identification information can allow the operator of a push service to contact the operator of the application server. The signature can be used to restrict the use of a push message subscription to a single application server.",
"authors": [
"M. Thomson",
"P. Beverloo"
],
"organizations": [],
"publication_date": "2017-11-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": "art",
"area_ru": "Приложения и взаимодействие в реальном времени",
"working_group": "webpush",
"source_draft": "draft-ietf-webpush-vapid-04",
"page_count": 14,
"doi": "10.17487/RFC8292",
"keywords": [
"authentication",
"restricted",
"restriction",
"signature"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8292/",
"html": "https://www.rfc-editor.org/rfc/rfc8292.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8292.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8292/"
}
}