Technology and engineering · 2020
RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
by R. Shekh-Yusef, C. Holmberg, V. Pascual
This document defines the "Bearer" authentication scheme for the Session Initiation Protocol (SIP) and a mechanism by which user authentication and SIP registration authorization is delegated to a third party, using the OAuth 2.0 framework and OpenID Connect Core 1.0. This document updates RFC 3261 to provide guidance on how a SIP User Agent Client (UAC) responds to a SIP 401/407 response that contains multiple WWW-Authenticate/Proxy-Authenticate header fields.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2020
- Status
- Proposed Standard
- Pages
- 15
- Updates
- RFC 3261
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.