draft-ietf-krb-wg-pad-00.txt   draft-ietf-krb-wg-pad-01.txt 
Internet Engineering Task Force S. Sorce, Ed. Internet Engineering Task Force S. Sorce, Ed.
Internet-Draft Red Hat Internet-Draft Red Hat
Intended status: Standards Track T. Yu, Ed. Intended status: Standards Track T. Yu, Ed.
Expires: August 11, 2012 T. Hardjono, Ed. Expires: August 12, 2012 T. Hardjono, Ed.
MIT Kerberos Consortium MIT Kerberos Consortium
Feb 8, 2012 Feb 9, 2012
Principal Authorization Data Containers POSIX Authorization Data
draft-ietf-krb-wg-pad-00 draft-ietf-krb-wg-pad-01
Abstract Abstract
This draft proposes a generalized authorization structure to transmit This document proposes a Kerberos Authorization Data element
authorization data for the Kerberos V5 protocol. Such an containing user and group directory information similar to that
authorization structure would allow for greater interoperability provided by RFC 2307, typically used by POSIX and POSIX-like systems
among directory services and other related Kerberos services across in the course of login type activities.
differing realms.
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 August 11, 2012. This Internet-Draft will expire on August 12, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Use-Case: Cross-Realm Directory Services . . . . . . . . . . . 4 3. Use-Case: Cross-Realm Directory Services . . . . . . . . . . . 3
4. A POSIX Authorization Structure for Kerberos V5 . . . . . . . 5 4. A POSIX Authorization Structure for Kerberos V5 . . . . . . . 4
4.1. Attributes . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Attributes . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. PAD-Realm . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. PAD-Realm . . . . . . . . . . . . . . . . . . . . . . . . 5
4.3. PAD-DNS-Domain . . . . . . . . . . . . . . . . . . . . . . 6 4.3. PAD-DNS-Domain . . . . . . . . . . . . . . . . . . . . . . 5
4.4. PAD-Short-Domain . . . . . . . . . . . . . . . . . . . . . 6 4.4. PAD-Short-Domain . . . . . . . . . . . . . . . . . . . . . 5
4.5. PAD-UDID . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.5. PAD-UDID . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.6. PAD-Posix-Username . . . . . . . . . . . . . . . . . . . . 7 4.6. PAD-Posix-Username . . . . . . . . . . . . . . . . . . . . 6
4.7. PAD-Posix-UID . . . . . . . . . . . . . . . . . . . . . . 7 4.7. PAD-Posix-UID . . . . . . . . . . . . . . . . . . . . . . 6
4.8. PAD-Posix-GID . . . . . . . . . . . . . . . . . . . . . . 7 4.8. PAD-Posix-GID . . . . . . . . . . . . . . . . . . . . . . 6
4.9. PAD-Posix-Gecos . . . . . . . . . . . . . . . . . . . . . 7 4.9. PAD-Posix-Gecos . . . . . . . . . . . . . . . . . . . . . 6
4.10. PAD-Posix-Homedir . . . . . . . . . . . . . . . . . . . . 7 4.10. PAD-Posix-Homedir . . . . . . . . . . . . . . . . . . . . 6
4.11. PAD-Posix-Shell . . . . . . . . . . . . . . . . . . . . . 7 4.11. PAD-Posix-Shell . . . . . . . . . . . . . . . . . . . . . 6
4.12. PAD-Fullname . . . . . . . . . . . . . . . . . . . . . . . 8 4.12. PAD-Fullname . . . . . . . . . . . . . . . . . . . . . . . 7
4.13. PAD-AlternateNames . . . . . . . . . . . . . . . . . . . . 8 4.13. PAD-AlternateNames . . . . . . . . . . . . . . . . . . . . 7
4.14. PAD-Groups . . . . . . . . . . . . . . . . . . . . . . . . 8 4.14. PAD-Groups . . . . . . . . . . . . . . . . . . . . . . . . 7
4.15. PAD Mapped Attributes . . . . . . . . . . . . . . . . . . 9 4.15. PAD Mapped Attributes . . . . . . . . . . . . . . . . . . 8
4.16. RFC2307 references for Directory Services backed KDCs . . 9 4.16. RFC2307 references for Directory Services backed KDCs . . 8
4.16.1. PAD-Posix-Username as 'uid' . . . . . . . . . . . . . 9 4.16.1. PAD-Posix-Username as 'uid' . . . . . . . . . . . . . 8
4.16.2. PAD-Posix-UID as 'uidNumber' . . . . . . . . . . . . 9 4.16.2. PAD-Posix-UID as 'uidNumber' . . . . . . . . . . . . 8
4.16.3. PAD-Posix-GID as 'gidNumber' . . . . . . . . . . . . 10 4.16.3. PAD-Posix-GID as 'gidNumber' . . . . . . . . . . . . 9
4.16.4. PAD-Posix-Gecos as 'gecos' . . . . . . . . . . . . . 10 4.16.4. PAD-Posix-Gecos as 'gecos' . . . . . . . . . . . . . 9
4.16.5. PAD-Posix-Homedir as 'homeDirectory' . . . . . . . . 10 4.16.5. PAD-Posix-Homedir as 'homeDirectory' . . . . . . . . 9
4.16.6. PAD-Posix-Shell as 'loginShell' . . . . . . . . . . . 10 4.16.6. PAD-Posix-Shell as 'loginShell' . . . . . . . . . . . 9
5. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. PAD Format . . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. PAD Format . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Data Structures and Extensions . . . . . . . . . . . . . . . . 12 7. Data Structures and Extensions . . . . . . . . . . . . . . . . 11
7.1. AD-ID-ANCHOR . . . . . . . . . . . . . . . . . . . . . . . 12 7.1. AD-ID-ANCHOR . . . . . . . . . . . . . . . . . . . . . . . 11
7.2. AD-PAD-DATA . . . . . . . . . . . . . . . . . . . . . . . 13 7.2. AD-PAD-DATA . . . . . . . . . . . . . . . . . . . . . . . 12
7.3. GSS-API Authenticator Extension . . . . . . . . . . . . . 13 7.3. GSS-API Authenticator Extension . . . . . . . . . . . . . 12
8. Assigned numbers . . . . . . . . . . . . . . . . . . . . . . . 14 8. Assigned numbers . . . . . . . . . . . . . . . . . . . . . . . 13
9. Timeouts Considerations . . . . . . . . . . . . . . . . . . . 14 9. Timeouts Considerations . . . . . . . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
11. Security Considerations . . . . . . . . . . . . . . . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 14
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
13.1. Normative References . . . . . . . . . . . . . . . . . . . 15 13.1. Normative References . . . . . . . . . . . . . . . . . . . 14
13.2. Informative References . . . . . . . . . . . . . . . . . . 16 13.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 16 Appendix A. Additional Stuff . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
There is an increasing need today for Kerberos to support the There is an increasing need today for Kerberos to support the
delivery and processing of authorization information pertaining to delivery and processing of authorization information pertaining to
the principals seeking access to the servers. Kerberos today is used the principals seeking access to the servers. Kerberos today is used
extensively for authentication to directory services within the extensively for authentication to directory services within the
Enterprise. In many cases, a directory service is implemented as a Enterprise. In many cases, a directory service is implemented as a
distributed database system organized across multiple realms. As distributed database system organized across multiple realms. As
such, when a client in one realm seeks access to a directory service such, when a client in one realm seeks access to a directory service
 End of changes. 6 change blocks. 
53 lines changed or deleted 52 lines changed or added

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