draft-ietf-kitten-krb-auth-indicator-00.txt   draft-ietf-kitten-krb-auth-indicator-01.txt 
Internet Engineering Task Force A. Jain Internet Engineering Task Force A. Jain
Internet-Draft Georgia Tech Internet-Draft Georgia Tech
Updates: 4120 (if approved) N. Kinder Updates: 4120 (if approved) N. Kinder
Intended status: Standards Track N. McCallum Intended status: Standards Track N. McCallum
Expires: August 21, 2015 Red Hat, Inc. Expires: November 17, 2016 Red Hat, Inc.
February 17, 2015 May 16, 2016
Authentication Indicator in Kerberos Tickets Authentication Indicator in Kerberos Tickets
draft-ietf-kitten-krb-auth-indicator-00 draft-ietf-kitten-krb-auth-indicator-01
Abstract Abstract
This document proposes an extension in the Kerberos protocol This document proposes an extension in the Kerberos protocol
[RFC4120]. It defines a new Authorization Data Type AD- [RFC4120]. It defines a new Authorization Data Type AD-
AUTHENTICATION-INDICATOR. The purpose of introducing this data type AUTHENTICATION-INDICATOR. The purpose of introducing this data type
is to include an indicator of the strength of a client's is to include an indicator of the strength of a client's
authentication in the service tickets so that the application authentication in the service tickets so that the application
services can use it as an input into policy decisions. services can use it as an input into policy decisions.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 21, 2015. This Internet-Draft will expire on November 17, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Conventions . . . . . . . . . . . . . . . . . . . . 2 2. Document Conventions . . . . . . . . . . . . . . . . . . . . 2
3. AD Type Specification . . . . . . . . . . . . . . . . . . . . 2 3. AD Type Specification . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Normative References . . . . . . . . . . . . . . . . . . 3 5.1. Normative References . . . . . . . . . . . . . . . . . . 4
5.2. Informative References . . . . . . . . . . . . . . . . . 4 5.2. Informative References . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 4
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
Kerberos [RFC4120] allows secure interaction among users and services Kerberos [RFC4120] allows secure interaction among users and services
over a network. It supports a variety of authentication mechanisms over a network. It supports a variety of authentication mechanisms
using its Pre-Authentication framework [RFC6113]. The Kerberos using its Pre-Authentication framework [RFC6113]. The Kerberos
Authentication Service has been architected to support password based Authentication Service has been architected to support password based
authentication as well as multi-factor authentication using One Time authentication as well as multi-factor authentication using One Time
Password devices or Public Key Cryptography. Implementations that Password devices or Public Key Cryptography. Implementations that
have Pre-Authentication mechanisms offering significantly different have Pre-Authentication mechanisms offering significantly different
strengths of client authentication may choose to keep track of the strengths of client authentication may choose to keep track of the
strength of the authentication used as an input into policy strength of the authentication used as an input into policy
decisions. This document proposes a new Authorization Data Type to decisions.
be used to convey the authentication strength to the application
services. The AD type is wrapped in the AD-CAMMAC This document proposes a new Authorization Data Type to be used to
[I-D.ietf-kitten-cammac] container and contains information about the convey the authentication strength to the application services. The
type of authentication mechanism used by the Kerberos client to KDC can provide the DER encoding of the ASN.1 type defined in this
authenticate itself to the KDC. document into the ad-data field of the AD-CAMMAC [RFC7751] container.
This ASN.1 type contains information about the type of authentication
mechanism used by the Kerberos client to authenticate itself to the
KDC.
2. Document Conventions 2. Document Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. AD Type Specification 3. AD Type Specification
The KDC MAY include the following Authorization Data element, wrapped The KDC MAY include the following Authorization Data element, wrapped
in AD-CAMMAC, in the initial credentials and copy it from a ticket- in AD-CAMMAC, in the initial credentials and copy it from a ticket-
granting ticket into service tickets: granting ticket into service tickets:
AD-AUTHENTICATION-INDICATOR TBD AD-AUTHENTICATION-INDICATOR 97
The corresponding ad-data field contains the DER encoding of the The corresponding ad-data field contains the DER encoding of the
ASN.1 type which is defined as ASN.1 type which is defined as
AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String
Each UTF8String value is a short string that indicates that a Each UTF8String value is a short string that indicates that a
particular set of requirements was met during the initial particular set of requirements was met during the initial
authentication. These strings are intended to be compared against authentication. These strings are intended to be compared against
known values. They are not intended to store structured data. These known values. They are not intended to store structured data. These
strings MAY be site-defined strings that do not contain a colon such strings MAY be site-defined strings that do not contain a colon such
skipping to change at page 4, line 5 skipping to change at page 4, line 9
Using multiple strings in AD-AUTHENTICATION-INDICATOR MAY lead to Using multiple strings in AD-AUTHENTICATION-INDICATOR MAY lead to
ambiguity when a service tries to make a decision based on the AD- ambiguity when a service tries to make a decision based on the AD-
AUTHENTICATION-INDICATOR values. This ambiguity can be avoided if AUTHENTICATION-INDICATOR values. This ambiguity can be avoided if
indicator values are always used as a positive indication of certain indicator values are always used as a positive indication of certain
requirements being met during the initial authentication. requirements being met during the initial authentication.
5. References 5. References
5.1. Normative References 5.1. Normative References
[I-D.ietf-kitten-cammac]
Sorce, S., Yu, T., and T. Hardjono, "Kerberos
Authorization Data Container Authenticated by Multiple
MACs", draft-ietf-kitten-cammac-01 (work in progress),
January 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The [RFC4120] Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The
Kerberos Network Authentication Service (V5)", RFC 4120, Kerberos Network Authentication Service (V5)", RFC 4120,
July 2005. DOI 10.17487/RFC4120, July 2005,
<http://www.rfc-editor.org/info/rfc4120>.
[RFC6113] Hartman, S. and L. Zhu, "A Generalized Framework for [RFC6113] Hartman, S. and L. Zhu, "A Generalized Framework for
Kerberos Pre-Authentication", RFC 6113, April 2011. Kerberos Pre-Authentication", RFC 6113, DOI 10.17487/
RFC6113, April 2011,
<http://www.rfc-editor.org/info/rfc6113>.
[RFC7751] Sorce, S. and T. Yu, "Kerberos Authorization Data
Container Authenticated by Multiple Message Authentication
Codes (MACs)", RFC 7751, DOI 10.17487/RFC7751, March 2016,
<http://www.rfc-editor.org/info/rfc7751>.
5.2. Informative References 5.2. Informative References
[MS-SFU] Microsoft, "Kerberos Protocol Extensions: Service for User [MS-SFU] Microsoft, "Kerberos Protocol Extensions: Service for User
and Constrained Delegation Protocol", January 2013, and Constrained Delegation Protocol", January 2013,
<http://msdn.microsoft.com/en-us/library/cc246071.aspx>. <http://msdn.microsoft.com/en-us/library/cc246071.aspx>.
[RFC6711] Johansson, L., "An IANA Registry for Level of Assurance [RFC6711] Johansson, L., "An IANA Registry for Level of Assurance
(LoA) Profiles", RFC 6711, August 2012. (LoA) Profiles", RFC 6711, DOI 10.17487/RFC6711, August
2012, <http://www.rfc-editor.org/info/rfc6711>.
Appendix A. Acknowledgements Appendix A. ASN.1 Module
KerberosV5AuthenticationIndicators {
iso(1) identified-organization(3) dod(6) internet(1)
security(5) kerberosV5(2) modules(4)
authentication-indicators(9)
} DEFINITIONS EXPLICIT TAGS ::= BEGIN
AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String
END
Appendix B. Acknowledgements
Dmitri Pal (Red Hat) Dmitri Pal (Red Hat)
Simo Sorce (Red Hat) Simo Sorce (Red Hat)
Authors' Addresses Authors' Addresses
Anupam Jain Anupam Jain
Georgia Tech Georgia Tech
225 North Ave NW 225 North Ave NW
Atlanta, GA 30332 Atlanta, GA 30332
 End of changes. 15 change blocks. 
27 lines changed or deleted 49 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/