Authentication Indicator in Kerberos Tickets
RFC 8129
| Document | Type |
RFC - Proposed Standard
(March 2017; No errata)
Updates RFC 4120
|
|
|---|---|---|---|
| Authors | Anupam Jain , Nathan Kinder , Nathaniel McCallum | ||
| Last updated | 2017-03-22 | ||
| Replaces | draft-jain-kitten-krb-auth-indicator | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Benjamin Kaduk | ||
| Shepherd write-up | Show (last changed 2016-11-17) | ||
| IESG | IESG state | RFC 8129 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Stephen Farrell | ||
| Send notices to | "Benjamin Kaduk" <kaduk@mit.edu> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) A. Jain
Request for Comments: 8129 Georgia Tech
Updates: 4120 N. Kinder
Category: Standards Track N. McCallum
ISSN: 2070-1721 Red Hat, Inc.
March 2017
Authentication Indicator in Kerberos Tickets
Abstract
This document updates RFC 4120, as it specifies an extension in the
Kerberos protocol. It defines a new authorization data type,
AD-AUTHENTICATION-INDICATOR. The purpose of introducing this data
type is to include an indicator of the strength of a client's
authentication in service tickets so that application services can
use it as an input into policy decisions.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8129.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Jain, et al. Standards Track [Page 1]
RFC 8129 Authentication Indicator March 2017
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Conventions . . . . . . . . . . . . . . . . . . . . 2
3. AD Type Specification . . . . . . . . . . . . . . . . . . . . 2
4. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Kerberos [RFC4120] allows secure interaction among users and services
over a network. It supports a variety of authentication mechanisms
using its pre-authentication framework [RFC6113]. The Kerberos
authentication service has been architected to support password-based
authentication as well as multi-factor authentication using one-time
password devices, public-key cryptography, and other
pre-authentication schemes. Implementations that offer
pre-authentication mechanisms supporting significantly different
strengths of client authentication may choose to keep track of the
strength of the authentication that was used, for use as an input
into policy decisions.
This document specifies a new authorization data type to convey
authentication strength information to application services.
Elements of this type appear within an AD-CAMMAC (Authorization Data
type Container Authenticated by Multiple Message Authentication
Codes) [RFC7751] container.
2. Document Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
3. AD Type Specification
The Key Distribution Center (KDC) MAY include authorization data of
ad-type 97, wrapped in AD-CAMMAC, in initial credentials. The KDC
MAY copy it from a ticket-granting ticket into service tickets.
Jain, et al. Standards Track [Page 2]
RFC 8129 Authentication Indicator March 2017
The corresponding ad-data field contains the DER encoding [X.690] of
the following ASN.1 [X.680] type:
AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String
Show full document text