Hardt, 2012 - Google Patents
Rfc 6749: The oauth 2.0 authorization frameworkHardt, 2012
- Document ID
- 3817896667238582436
- Author
- Hardt D
- Publication year
External Links
Snippet
The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the …
- 230000003993 interaction 0 abstract description 11
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements or protocols for real-time communications
- H04L65/10—Signalling, control or architecture
- H04L65/1013—Network architectures, gateways, control or user entities
- H04L65/1046—Call controllers; Call servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements or protocols for real-time communications
- H04L65/10—Signalling, control or architecture
- H04L65/1003—Signalling or session protocols
- H04L65/1006—SIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L29/00—Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
- H04L29/02—Communication control; Communication processing contains provisionally no documents
- H04L29/06—Communication control; Communication processing contains provisionally no documents characterised by a protocol
- H04L29/0602—Protocols characterised by their application
- H04L29/06027—Protocols for multimedia communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements or protocols for real-time communications
- H04L65/10—Signalling, control or architecture
- H04L65/1013—Network architectures, gateways, control or user entities
- H04L65/102—Gateways
- H04L65/1033—Signalling gateways
- H04L65/104—Signalling gateways at the edge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements or protocols for real-time communications
- H04L65/10—Signalling, control or architecture
- H04L65/1013—Network architectures, gateways, control or user entities
- H04L65/1043—MGC, MGCP or Megaco
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements or protocols for real-time communications
- H04L65/10—Signalling, control or architecture
- H04L65/1013—Network architectures, gateways, control or user entities
- H04L65/102—Gateways
- H04L65/1023—Media gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network-specific arrangements or communication protocols supporting networked applications
- H04L67/02—Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Hardt | Rfc 6749: The oauth 2.0 authorization framework | |
Hammer-Lahav | The oauth 1.0 protocol | |
Jones et al. | The oauth 2.0 authorization framework: Bearer token usage | |
Lodderstedt et al. | OAuth 2.0 threat model and security considerations | |
Sakimura et al. | OpenID Connect Core 1.0 incorporating errata set 1 | |
KR101414312B1 (en) | Policy driven, credntial delegat10n for single sign on and secure access to network resources | |
Hammer-Lahav | Rfc 5849: The oauth 1.0 protocol | |
CN103220303B (en) | The login method of server and server, authenticating device | |
CN113645247A (en) | Authority authentication control method based on HTTP (hyper text transport protocol) and storage medium | |
US20150328119A1 (en) | Method of treating hair | |
US20150281211A1 (en) | Network security | |
Singh et al. | OAuth 2.0: Architectural design augmentation for mitigation of common security vulnerabilities | |
Sadqi et al. | Web oauth-based SSO systems security | |
Lodderstedt et al. | OAuth 2.0 Security Best Current Practice (draft-ietf-oauth-security-topics-16) | |
Jones et al. | RFC 6750: The OAuth 2.0 authorization framework: Bearer token usage | |
Phan | Service oriented architecture (soa)-security challenges and mitigation strategies | |
Deeptha et al. | Extending OpenID connect towards mission critical applications | |
Farrell et al. | HTTP Origin-Bound Authentication (HOBA) | |
Corella et al. | Security analysis of double redirection protocols | |
Parecki | The Little Book of OAuth 2.0 RFCs | |
Schwenk et al. | The power of recognition: secure single sign-on using TLS channel bindings | |
Maidine et al. | Cloud Identity Management Mechanisms and Issues | |
Ofleh | Future of Identity and Access Management: The OpenID Connect Protocol | |
Nazir et al. | Security measures needed for exposing Restful services through OAuth 2 | |
Χριστινάκης | Auditing and extending security features of OAuth 2.0 framework |