RFC 7751: Kerberos Authorization Data Container Authenticated by Multiple Message Authentication Codes (MACs)
In plain English — editorial summary, not part of the RFC
This document specifies a Kerberos authorization data container that supersedes AD-KDC-ISSUED. It allows for multiple Message Authentication Codes (MACs) or signatures to authenticate the contained authorization data elements. The multiple MACs are needed to mitigate shortcomings in the existing AD-KDC-ISSUED container. This document updates RFC 4120.
Document record
- Document ID
- RFC7751
- Published
- March 2016
- Authors
- S. Sorce; T. Yu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 4120
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6880An Information Model for Kerberos Version 5Current
March 2013
- RFC 6803Camellia Encryption for Kerberos 5Current
November 2012
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
- RFC 1510The Kerberos Network Authentication Service (V5)Obsoleted
September 1993
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 7744Use Cases for Authentication and Authorization in Constrained EnvironmentsCurrent
January 2016
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
- RFC 7800Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)Current
April 2016
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?