d1972b5179
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@14336 ec53bebd-3082-4978-b11e-865c3cabbd6b
432 lines
8.0 KiB
Plaintext
432 lines
8.0 KiB
Plaintext
NETWORK WORKING GROUP N. Williams
|
|
Internet-Draft Sun
|
|
Expires: December 30, 2004 July 2004
|
|
|
|
|
|
|
|
GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS
|
|
Mechanism
|
|
draft-williams-krb5-gssapi-domain-based-names-00.txt
|
|
|
|
|
|
Status of this Memo
|
|
|
|
|
|
By submitting this Internet-Draft, I certify that any applicable
|
|
patent or other IPR claims of which I am aware have been disclosed,
|
|
and any of which I become aware will be disclosed, in accordance with
|
|
RFC 3668.
|
|
|
|
|
|
Internet-Drafts are working documents of the Internet Engineering
|
|
Task Force (IETF), its areas, and its working groups. Note that
|
|
other groups may also distribute working documents as
|
|
Internet-Drafts.
|
|
|
|
|
|
Internet-Drafts are draft documents valid for a maximum of six months
|
|
and may be updated, replaced, or obsoleted by other documents at any
|
|
time. It is inappropriate to use Internet-Drafts as reference
|
|
material or to cite them other than as "work in progress."
|
|
|
|
|
|
The list of current Internet-Drafts can be accessed at
|
|
http://www.ietf.org/ietf/1id-abstracts.txt.
|
|
|
|
|
|
The list of Internet-Draft Shadow Directories can be accessed at
|
|
http://www.ietf.org/shadow.html.
|
|
|
|
|
|
This Internet-Draft will expire on December 30, 2004.
|
|
|
|
|
|
Copyright Notice
|
|
|
|
|
|
Copyright (C) The Internet Society (2004). All Rights Reserved.
|
|
|
|
|
|
Abstract
|
|
|
|
|
|
This document describes the mapping of GSS-API domainname-based
|
|
service principal names onto Kerberos V principal names.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 1]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
Table of Contents
|
|
|
|
|
|
1. Conventions used in this document . . . . . . . . . . . . . . . 3
|
|
2. Domain-Based Names for the Kerberos V GSS-API Mechanism . . . . 4
|
|
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
|
|
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
|
|
5. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
|
|
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
|
|
Intellectual Property and Copyright Statements . . . . . . . . . 7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 2]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
1. Conventions used in this document
|
|
|
|
|
|
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 [RFC2119].
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 3]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
2. Domain-Based Names for the Kerberos V GSS-API Mechanism
|
|
|
|
|
|
In accordance with [DOMAIN-BASED-NAMES] this document provides the
|
|
mechanism-specific details needed to implement GSS-API [RFC2743]
|
|
domain-based service names with the Kerberos V GSS-API mechanism
|
|
[RFC1964].
|
|
|
|
|
|
GSS_C_NT_DOMAINBASED_SERVICE name are mapped to Kerberos V principal
|
|
names as follows:
|
|
o the <service> name becomes the first (0th) component of the
|
|
Kerberos V principal name;
|
|
o the <domain> name becomes the second component of the Kerberos V
|
|
principal name; if the <domain> name is missing in the GSS name
|
|
then a default domain name MUST be substituted (though no
|
|
mechanism for determining this default is given here; this is an
|
|
implementation-specific detail);
|
|
o the <hostname>, if present, becomes the third component of the
|
|
Kerberos V principal name;
|
|
o the realm of the resulting principal name is that which
|
|
corresponds to the domain name, treated as a hostname, or, if none
|
|
can be determined in this way, then the realm of the hostname, if
|
|
present, and, finally, if that is not possible, the default realm
|
|
for the GSS-API caller.
|
|
|
|
|
|
The same name canonicalization considerations and methods as used
|
|
elsewhere in the Kerberos V GSS-API mechanism [RFC1964] and Kerberos
|
|
V [RFC1510] in general apply here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 4]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
3. Examples
|
|
|
|
|
|
o "ldap@@ds1.example.tld" may map to "ldap/example.tld/
|
|
ds1.example.tld@EXAMPLE.TLD"
|
|
o "ldap@example.tld@ds1.example.tld" may map to "ldap/example.tld/
|
|
ds1.example.tld@EXAMPLE.TLD"
|
|
|
|
|
|
o "kadmin@@kdc1.example.tld" may map to "kadmin/example.tld/
|
|
kdc1.example.tld@EXAMPLE.TLD"
|
|
o "kadmin@example.tld@kdc1.example.tld" may map to "kadmin/
|
|
example.tld/kdc1.example.tld@EXAMPLE.TLD"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 5]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
4. Security Considerations
|
|
|
|
|
|
See [DOMAIN-BASED-NAMES].
|
|
|
|
|
|
5 Normative
|
|
|
|
|
|
[RFC1510] Kohl, J. and B. Neuman, "The Kerberos Network
|
|
Authentication Service (V5)", RFC 1510, September 1993.
|
|
|
|
|
|
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC
|
|
1964, June 1996.
|
|
|
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
|
|
Requirement Levels", BCP 14, RFC 2119, March 1997.
|
|
|
|
|
|
[RFC2743] Linn, J., "Generic Security Service Application Program
|
|
Interface Version 2, Update 1", RFC 2743, January 2000.
|
|
|
|
|
|
|
|
Author's Address
|
|
|
|
|
|
Nicolas Williams
|
|
Sun Microsystems
|
|
5300 Riata Trace Ct
|
|
Austin, TX 78727
|
|
US
|
|
|
|
|
|
EMail: Nicolas.Williams@sun.com
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 6]
|
|
Internet-Draft Kerberos Domain Based Names July 2004
|
|
|
|
|
|
|
|
Intellectual Property Statement
|
|
|
|
|
|
The IETF takes no position regarding the validity or scope of any
|
|
Intellectual Property Rights or other rights that might be claimed to
|
|
pertain to the implementation or use of the technology described in
|
|
this document or the extent to which any license under such rights
|
|
might or might not be available; nor does it represent that it has
|
|
made any independent effort to identify any such rights. Information
|
|
on the procedures with respect to rights in RFC documents can be
|
|
found in BCP 78 and BCP 79.
|
|
|
|
|
|
Copies of IPR disclosures made to the IETF Secretariat and any
|
|
assurances of licenses to be made available, or the result of an
|
|
attempt made to obtain a general license or permission for the use of
|
|
such proprietary rights by implementers or users of this
|
|
specification can be obtained from the IETF on-line IPR repository at
|
|
http://www.ietf.org/ipr.
|
|
|
|
|
|
The IETF invites any interested party to bring to its attention any
|
|
copyrights, patents or patent applications, or other proprietary
|
|
rights that may cover technology that may be required to implement
|
|
this standard. Please address the information to the IETF at
|
|
ietf-ipr@ietf.org.
|
|
|
|
|
|
|
|
Disclaimer of Validity
|
|
|
|
|
|
This document and the information contained herein are provided on an
|
|
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
|
|
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
|
|
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
|
|
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
|
|
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
|
|
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
|
|
|
|
|
|
|
|
Copyright Statement
|
|
|
|
|
|
Copyright (C) The Internet Society (2004). This document is subject
|
|
to the rights, licenses and restrictions contained in BCP 78, and
|
|
except as set forth therein, the authors retain all their rights.
|
|
|
|
|
|
|
|
Acknowledgment
|
|
|
|
|
|
Funding for the RFC Editor function is currently provided by the
|
|
Internet Society.
|
|
|
|
|
|
|
|
|
|
Williams Expires December 30, 2004 [Page 7] |