draft-ietf-kitten-krb-auth-indicator-05.txt   draft-ietf-kitten-krb-auth-indicator-06.txt 
Internet Engineering Task Force A. Jain Internet Engineering Task Force A. Jain
Internet-Draft Georgia Tech Internet-Draft Georgia Tech
Updates: 7751 (if approved) N. Kinder Updates: 4120 (if approved) N. Kinder
Intended status: Standards Track N. McCallum Intended status: Standards Track N. McCallum
Expires: July 7, 2017 Red Hat, Inc. Expires: July 8, 2017 Red Hat, Inc.
January 3, 2017 January 4, 2017
Authentication Indicator in Kerberos Tickets Authentication Indicator in Kerberos Tickets
draft-ietf-kitten-krb-auth-indicator-05 draft-ietf-kitten-krb-auth-indicator-06
Abstract Abstract
This document updates section "6. Assigned Numbers" of RFC 7751 in This document updates RFC 4120 in order to specify an extension in
order to specify an extension in the Kerberos protocol. It defines a the Kerberos protocol. It defines a new authorization data type AD-
new authorization data type AD-AUTHENTICATION-INDICATOR. The purpose AUTHENTICATION-INDICATOR. The purpose of introducing this data type
of introducing this data type is to include an indicator of the is to include an indicator of the strength of a client's
strength of a client's authentication in service tickets so that authentication in service tickets so that application services can
application services can use it as an input into policy decisions. use it as an input into policy decisions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 7, 2017. This Internet-Draft will expire on July 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 2, line 13 skipping to change at page 2, line 13
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 . . . . . . . . . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . 4
Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
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, public-key cryptography and other pre- password devices, public-key cryptography and other pre-
authentication schemes. Implementations that offer pre- authentication schemes. Implementations that offer pre-
skipping to change at page 3, line 27 skipping to change at page 3, line 27
* A site-defined string, which MUST NOT contain a colon, whose * A site-defined string, which MUST NOT contain a colon, whose
meaning is determined by the realm administrator. meaning is determined by the realm administrator.
Authorization data elements of type AD-AUTHENTICATION-INDICATOR MUST Authorization data elements of type AD-AUTHENTICATION-INDICATOR MUST
be included in an AD-CAMMAC container so that their contents can be be included in an AD-CAMMAC container so that their contents can be
verified as originating from the KDC. Elements of type AD- verified as originating from the KDC. Elements of type AD-
AUTHENTICATION-INDICATOR MAY safely be ignored by applications and AUTHENTICATION-INDICATOR MAY safely be ignored by applications and
KDCs that do not implement this element. KDCs that do not implement this element.
4. Security Considerations 4. Assigned Numbers
RFC 4120 [RFC4120] is updated in the following way:
o The ad-type number 97 is assigned for AD-AUTHENTICATION-INDICATOR,
updating the table in Section 7.5.4 of RFC 4120 [RFC4120].
o The table in Section 5.2.6 of RFC 4120 [RFC4120] is updated to map
the ad-type 97 to "DER encoding of AD-AUTHENTICATION-INDICATOR".
5. Security Considerations
Elements of type AD-AUTHENTICATION-INDICATOR are wrapped in AD-CAMMAC Elements of type AD-AUTHENTICATION-INDICATOR are wrapped in AD-CAMMAC
containers. AD-CAMMAC supersedes AD-KDC-ISSUED, and allows both containers. AD-CAMMAC supersedes AD-KDC-ISSUED, and allows both
application services and the KDC to verify the authenticity of the application services and the KDC to verify the authenticity of the
contained authorization data. contained authorization data.
KDC implementations MUST use AD-CAMMAC verifiers as described in the KDC implementations MUST use AD-CAMMAC verifiers as described in the
the security considerations of RFC 7751 [RFC7751] to ensure that AD- the security considerations of RFC 7751 [RFC7751] to ensure that AD-
AUTHENTICATION-INDICATOR elements are not modified by an attacker. AUTHENTICATION-INDICATOR elements are not modified by an attacker.
Application servers MUST validate the AD-CAMMAC container before Application servers MUST validate the AD-CAMMAC container before
skipping to change at page 4, line 7 skipping to change at page 4, line 18
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. For requirements being met during the initial authentication. For
example, if a "without-password" indicator is inserted whenever example, if a "without-password" indicator is inserted whenever
authentication occurs without a password, a service might assume this authentication occurs without a password, a service might assume this
is an indication that a higher-strength client authentication is an indication that a higher-strength client authentication
occurred. However, this indicator might also be inserted when no occurred. However, this indicator might also be inserted when no
authentication occurred at all (such as anonymous PKINIT). authentication occurred at all (such as anonymous PKINIT).
Service evaluation of site-defined indicators MUST consider the realm Service evaluation of site-defined indicators MUST consider the realm
of original authentication in order to avoid cross-realm indicator of original authentication in order to avoid cross-realm indicator
collision. Failure to enforce this property can result in invalid collisions. Failure to enforce this property can result in invalid
authorization. authorization.
5. IANA Considerations 6. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
6. References 7. References
6.1. Normative References 7.1. Normative References
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <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,
DOI 10.17487/RFC4120, July 2005, DOI 10.17487/RFC4120, July 2005,
<http://www.rfc-editor.org/info/rfc4120>. <http://www.rfc-editor.org/info/rfc4120>.
skipping to change at page 4, line 38 skipping to change at page 5, line 5
[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, Kerberos Pre-Authentication", RFC 6113,
DOI 10.17487/RFC6113, April 2011, DOI 10.17487/RFC6113, April 2011,
<http://www.rfc-editor.org/info/rfc6113>. <http://www.rfc-editor.org/info/rfc6113>.
[RFC7751] Sorce, S. and T. Yu, "Kerberos Authorization Data [RFC7751] Sorce, S. and T. Yu, "Kerberos Authorization Data
Container Authenticated by Multiple Message Authentication Container Authenticated by Multiple Message Authentication
Codes (MACs)", RFC 7751, DOI 10.17487/RFC7751, March 2016, Codes (MACs)", RFC 7751, DOI 10.17487/RFC7751, March 2016,
<http://www.rfc-editor.org/info/rfc7751>. <http://www.rfc-editor.org/info/rfc7751>.
6.2. Informative References 7.2. Informative References
[RFC6711] Johansson, L., "An IANA Registry for Level of Assurance [RFC6711] Johansson, L., "An IANA Registry for Level of Assurance
(LoA) Profiles", RFC 6711, DOI 10.17487/RFC6711, August (LoA) Profiles", RFC 6711, DOI 10.17487/RFC6711, August
2012, <http://www.rfc-editor.org/info/rfc6711>. 2012, <http://www.rfc-editor.org/info/rfc6711>.
Appendix A. ASN.1 Module Appendix A. ASN.1 Module
KerberosV5AuthenticationIndicators { KerberosV5AuthenticationIndicators {
iso(1) identified-organization(3) dod(6) internet(1) iso(1) identified-organization(3) dod(6) internet(1)
security(5) kerberosV5(2) modules(4) security(5) kerberosV5(2) modules(4)
 End of changes. 12 change blocks. 
25 lines changed or deleted 36 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/