RFC 7056: Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism
In plain English — editorial summary, not part of the RFC
The naming extensions to the Generic Security Service Application Programming Interface (GSS-API) provide a mechanism for applications to discover authorization and personalization information associated with GSS-API names. The Extensible Authentication Protocol GSS-API mechanism allows an Authentication, Authorization, and Accounting (AAA) peer to provide authorization attributes alongside an authentication response. It also supplies mechanisms to process Security Assertion Markup Language (SAML) messages provided in the AAA response. This document describes how to use the Naming Extensions API to access that information.
Document record
- Document ID
- RFC7056
- Published
- December 2013
- Authors
- S. Hartman; J. Howlett
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7055A GSS-API Mechanism for the Extensible Authentication ProtocolCurrent
December 2013
- RFC 7057Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)Current
December 2013
- RFC 7030Enrollment over Secure TransportUpdated
October 2013
- RFC 7029Extensible Authentication Protocol (EAP) Mutual Cryptographic BindingCurrent
October 2013
- RFC 7018Auto-Discovery VPN Problem Statement and RequirementsCurrent
September 2013
- RFC 7009OAuth 2.0 Token RevocationCurrent
August 2013
- RFC 6989Additional Diffie-Hellman Tests for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2013
- RFC 6961The Transport Layer Security (TLS) Multiple Certificate Status Request ExtensionObsoleted
June 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?