draft-ietf-kitten-gssapi-naming-exts-00.txt   draft-ietf-kitten-gssapi-naming-exts-01.txt 
NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: November 14, 2005 May 13, 2005 Expires: April 17, 2006 October 14, 2005
GSS-API Naming Extensions GSS-API Naming Extensions
draft-ietf-kitten-gssapi-naming-exts-00.txt draft-ietf-kitten-gssapi-naming-exts-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 31 skipping to change at page 1, line 33
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 14, 2005. This Internet-Draft will expire on April 17, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
The Generic Security Services API (GSS-API) provides a simple naming The Generic Security Services API (GSS-API) provides a simple naming
architecture that supports name-based authorization. This document architecture that supports name-based authorization. This document
introduces new APIs that extend the GSS-API naming and authorization introduces new APIs that extend the GSS-API naming and authorization
model. model.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
3. Name Attribute Sources and Criticality . . . . . . . . . . . 3 3. Name Attribute Sources and Criticality . . . . . . . . . . 3
4. Name Attributes/Values as ACL Subjects . . . . . . . . . . . 4 4. Name Attributes/Values as ACL Subjects . . . . . . . . . . 4
5. Mapping Mechanism Facilities to Name Attributes . . . . . . 4 5. Mapping Mechanism Facilities to Name Attributes . . . . . 4
5.1 Kerberos V and SPKM Authorization-Data . . . . . . . . . . . 4 5.1. Kerberos V and SPKM Authorization-Data . . . . . . . . . . 4
5.2 Kerberos V Cross-Realm Transit Paths . . . . . . . . . . . . 5 5.2. Kerberos V Cross-Realm Transit Paths . . . . . . . . . . . 5
5.3 PKIX Certificate Extensions . . . . . . . . . . . . . . . . 5 5.3. PKIX Certificate Extensions . . . . . . . . . . . . . . . 5
5.3.1 PKIX EKUs . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.3.1. PKIX EKUs . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3.2 PKIX Certificate Alternative Names . . . . . . . . . . . . . 6 5.3.2. PKIX Certificate Alternative Names . . . . . . . . . . . . 6
5.3.3 Other PKIX Certificate Extensions and Attributes . . . . . . 6 5.3.3. Other PKIX Certificate Extensions and Attributes . . . . . 6
5.4 PKIX Certificate CA Paths and Trust Anchors . . . . . . . . 6 5.4. PKIX Certificate CA Paths and Trust Anchors . . . . . . . 6
6. GSS_Inquire_name_attribute() . . . . . . . . . . . . . . . . 6 6. GSS_Inquire_name_attribute() . . . . . . . . . . . . . . . 6
6.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 7 7. GSS_Display_name_ext() . . . . . . . . . . . . . . . . . . 8
7. GSS_Display_name_ext() . . . . . . . . . . . . . . . . . . . 7 7.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. GSS_Inquire_name() . . . . . . . . . . . . . . . . . . . . 9
7.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 9
8. GSS_Inquire_name() . . . . . . . . . . . . . . . . . . . . . 8 9. GSS_Get_name_attribute() . . . . . . . . . . . . . . . . . 10
8.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 11
8.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 10 10. GSS_Set_name_attribute() . . . . . . . . . . . . . . . . . 11
9. GSS_Get_name_attribute() . . . . . . . . . . . . . . . . . . 10 10.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 11 11. GSS_Delete_name_attribute() . . . . . . . . . . . . . . . 12
9.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 11 11.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13
10. GSS_Set_name_attribute() . . . . . . . . . . . . . . . . . . 12 12. GSS_Export_name_composite() . . . . . . . . . . . . . . . 13
10.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 12 12.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 14
10.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 12 13. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . 14
11. GSS_Delete_name_attribute() . . . . . . . . . . . . . . . . 13 13.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 15
11.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 13 14. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . 15
11.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 13 14.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 16
12. GSS_Export_name_composite() . . . . . . . . . . . . . . . . 14 15. IANA Considerations . . . . . . . . . . . . . . . . . . . 16
12.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 14 16. Security Considerations . . . . . . . . . . . . . . . . . 17
12.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 14 17. Normative References . . . . . . . . . . . . . . . . . . . 17
13. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . 18
13.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 15 Intellectual Property and Copyright Statements . . . . . . 19
13.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 16
14. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . . 16
14.1 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 16
14.2 Java Bindings . . . . . . . . . . . . . . . . . . . . . . . 17
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . 17
16. Security Considerations . . . . . . . . . . . . . . . . . . 17
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
17.1 Normative References . . . . . . . . . . . . . . . . . . . . 18
17.2 Informative References . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . 20
1. Conventions used in this document 1. Conventions used in this document
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
As described in [I-D.GSS-NAMING] the GSS-API's naming architecture As described in [I-D.GSS-NAMING] the GSS-API's naming architecture
suffers from certain limitations. This document proposes concrete suffers from certain limitations. This document proposes concrete
GSS-API extensions as outlined in [I-D.GSS-NAMING]. GSS-API extensions as outlined in [I-D.GSS-NAMING].
A number of extensions to the GSS-API are described herein with the A number of extensions to the GSS-API [RFC2743] and its C Bindings
goal of making authorization information, and other information that [RFC2744] are described herein with the goal of making authorization
can be modelled as "name attributes" available as such to information, and other information that can be modelled as "name
applications. For example, Kerberos V authorization data elements, attributes" available as such to applications. For example, Kerberos
both, in their raw forms as well as mapped to more useful value V authorization data elements, both, in their raw forms as well as
types, can be made available to GSS-API applications through these mapped to more useful value types, can be made available to GSS-API
interfaces. applications through these interfaces.
The model is that GSS names have attributes. The attributes of a The model is that GSS names have attributes. The attributes of a
name may be authenticated by the credential whence the name comes, or name may be authenticated by the credential whence the name comes, or
may have been set locally on a GSS name for the purpose of may have been set locally on a GSS name for the purpose of
"asserting" the attribute during credential acquisition or security "asserting" the attribute during credential acquisition or security
context exchange. Name attributes' values are network context exchange. Name attributes' values are network
representations thereof (e.g., the actual value octets of the representations thereof (e.g., the actual value octets of the
contents of an X.509 certificate extension, for example) and are contents of an X.509 certificate extension, for example) and are
intended to be useful for constructing portable access control intended to be useful for constructing portable access control
facilities. Applications may often require language- or platform- facilities. Applications may often require language- or platform-
skipping to change at page 4, line 40 skipping to change at page 4, line 42
Public-Key GSS-API Mechanism, SPKM [RFC2025], both support the Public-Key GSS-API Mechanism, SPKM [RFC2025], both support the
concept and encoding of containers of "authorization-data" as concept and encoding of containers of "authorization-data" as
described in [I-D.ietf-krb-wg-kerberos-clarifications]. described in [I-D.ietf-krb-wg-kerberos-clarifications].
PKIX [RFC3280] supports a number of authorization-data-like features, PKIX [RFC3280] supports a number of authorization-data-like features,
like Extended Key Usage values (EKUs) and certificate extensions. like Extended Key Usage values (EKUs) and certificate extensions.
The authorization data can be accessed through the GSS-API name The authorization data can be accessed through the GSS-API name
attributes facility defined herein. attributes facility defined herein.
5.1 Kerberos V and SPKM Authorization-Data 5.1. Kerberos V and SPKM Authorization-Data
Authorization-data non-container elements asserted in Kerberos V AP- Authorization-data non-container elements asserted in Kerberos V AP-
REQ Authenticators MUST be mapped into *asserted* GSS-API name REQ Authenticators MUST be mapped into *asserted* GSS-API name
attributes; if not contained in AD-IF-RELEVANT then they MUST be attributes; if not contained in AD-IF-RELEVANT then they MUST be
mapped into *critical* GSS-API name attributes. AD-AND-OR mapped into *critical* GSS-API name attributes. AD-AND-OR
authorization-data elements MUST be mapped into a single *critical* authorization-data elements MUST be mapped into a single *critical*
attribute, (TBD). attribute, (TBD).
Authorization-data included in Kerberos V Tickets that is not Authorization-data included in Kerberos V Tickets that is not
contained in AD-KDCIssued (with valid signature) MUST be mapped into contained in AD-KDCIssued (with valid signature) MUST be mapped into
skipping to change at page 5, line 16 skipping to change at page 5, line 21
As with authorization-data elements in Authenticators, authorization- As with authorization-data elements in Authenticators, authorization-
data elements in Tickets not contained in AD-IF-RELEVANT are to be data elements in Tickets not contained in AD-IF-RELEVANT are to be
mapped to *critical* name attributes, and similarly with AD-AND-OR mapped to *critical* name attributes, and similarly with AD-AND-OR
(see above). (see above).
The OIDs for authorization-data elements are to be the authorization- The OIDs for authorization-data elements are to be the authorization-
data element's 'ad-type' integer ID, relative to the base OID <TBD> data element's 'ad-type' integer ID, relative to the base OID <TBD>
[NOTE: what about negative ad-type's? OID arcs are positive [NOTE: what about negative ad-type's? OID arcs are positive
integers... ad-type is an Int32, so clearly something can be done.] integers... ad-type is an Int32, so clearly something can be done.]
5.2 Kerberos V Cross-Realm Transit Paths 5.2. Kerberos V Cross-Realm Transit Paths
[Add text on how to represent/encode/interpret krb5 realm transit [Add text on how to represent/encode/interpret krb5 realm transit
paths as name attribute values. And text on PKINIT too... Basically paths as name attribute values. And text on PKINIT too... Basically
Ticket's 'transited' field should be exposed as an authenticated name Ticket's 'transited' field should be exposed as an authenticated name
attribute, with some uncompressed encoding, possibly encompassing attribute, with some uncompressed encoding, possibly encompassing
certificate validation paths of client certs used for PKINIT, with certificate validation paths of client certs used for PKINIT, with
criticality determined by the presence of the transit-policy-checked criticality determined by the presence of the transit-policy-checked
flag.] flag.]
5.3 PKIX Certificate Extensions 5.3. PKIX Certificate Extensions
[NOTE: In the Kerberos V authorization-data case we can tell when AD [NOTE: In the Kerberos V authorization-data case we can tell when AD
elements are "authenticated" and when the are asserted, but what elements are "authenticated" and when the are asserted, but what
about x.509 certificate extensions? Clearly KU, EKUs and about x.509 certificate extensions? Clearly KU, EKUs and
subjectAltNames are authenticated in that no CA should sign a cert subjectAltNames are authenticated in that no CA should sign a cert
with, say, arbitrary subjectAltNames not understood by the CA, but, with, say, arbitrary subjectAltNames not understood by the CA, but,
does that also apply to all other x.509 certificate extensions? The does that also apply to all other x.509 certificate extensions? The
answer may depend on actual CA operator practices... At worst a new answer may depend on actual CA operator practices... At worst a new
extension may be needed, like Kerberos V's AD-KDCIssued AD container extension may be needed, like Kerberos V's AD-KDCIssued AD container
element; at best this text can just say "all cert extensions MUST be element; at best this text can just say "all cert extensions MUST be
skipping to change at page 5, line 48 skipping to change at page 6, line 5
PKI certificate extensions MAY/SHOULD/MUST (see comment above) be PKI certificate extensions MAY/SHOULD/MUST (see comment above) be
mapped to *authenticated* GSS-API name attributes with the _same_ mapped to *authenticated* GSS-API name attributes with the _same_
OIDs, and if they be marked critical in the certificate then they OIDs, and if they be marked critical in the certificate then they
MUST be mapped as *critical* GSS-API name attributes. MUST be mapped as *critical* GSS-API name attributes.
SubjectAltNames and EKUs, specifically, MUST be mapped to SubjectAltNames and EKUs, specifically, MUST be mapped to
*authenticated* GSS-API name attributes; see below. Certificate *authenticated* GSS-API name attributes; see below. Certificate
extensions MUST be mapped to GSS-API name attributes whose OIDs are extensions MUST be mapped to GSS-API name attributes whose OIDs are
the same as the extensions' the same as the extensions'
5.3.1 PKIX EKUs 5.3.1. PKIX EKUs
Extended Key Usage extensions, specifically, MUST be mapped as Extended Key Usage extensions, specifically, MUST be mapped as
described above, except that GSS-API name attributes for EKUs MUST described above, except that GSS-API name attributes for EKUs MUST
have NULL values (i.e., zero-length OCTET STRINGs). have NULL values (i.e., zero-length OCTET STRINGs).
PKI certificate key usages (KUs, but not EKUs), MUST NOT be mapped to PKI certificate key usages (KUs, but not EKUs), MUST NOT be mapped to
GSS-API name attributes. GSS-API name attributes.
5.3.2 PKIX Certificate Alternative Names 5.3.2. PKIX Certificate Alternative Names
PKI certificate subjectAltNames MUST be mapped as *authenticated*, PKI certificate subjectAltNames MUST be mapped as *authenticated*,
*non-critical* GSS-API name attributes. *non-critical* GSS-API name attributes.
PKI certificate extensions MUST be mapped to *authenticated* GSS-API PKI certificate extensions MUST be mapped to *authenticated* GSS-API
name attributes with the _same_ OIDs, and if they be marked critical name attributes with the _same_ OIDs, and if they be marked critical
in the certificate then they MUST be mapped as *critical* GSS-API in the certificate then they MUST be mapped as *critical* GSS-API
name attributes. name attributes.
Extended Key Usage extensions, specifically, MUST be mapped as Extended Key Usage extensions, specifically, MUST be mapped as
described above, except that GSS-API name attributes for EKUs MUST described above, except that GSS-API name attributes for EKUs MUST
have NULL values (i.e., zero-length OCTET STRINGs). have NULL values (i.e., zero-length OCTET STRINGs).
5.3.3 Other PKIX Certificate Extensions and Attributes 5.3.3. Other PKIX Certificate Extensions and Attributes
[Add text...] [Add text...]
5.4 PKIX Certificate CA Paths and Trust Anchors 5.4. PKIX Certificate CA Paths and Trust Anchors
[Add text on how to represent/encode/interpret PKI certificate [Add text on how to represent/encode/interpret PKI certificate
validation CA paths as name attribute values, much as with Kerberos V validation CA paths as name attribute values, much as with Kerberos V
transited paths.] transited paths.]
6. GSS_Inquire_name_attribute() 6. GSS_Inquire_name_attribute()
[NOTE: This function was somewhat controversial at IETF63; we should
decide whether to remove it at IETF64. The controversy was, as I
recall over whether reflection functionality might not be dangerous,
leading to construction of inappropriate ACLs through dumb UIs. For
now I am making some changes to it: adding a NAME object as an input
parameter and some output parameters.]
Inputs: Inputs:
o name NAME
o attr OBJECT IDENTIFIER o attr OBJECT IDENTIFIER
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o attr_name OCTET STRING, o attr_name OCTET STRING, -- display name of the attribute
o attr_description OCTET STRING, o attr_description OCTET STRING, -- description of the attribute
o attr_is_a_name BOOLEAN, o attr_values_ordered BOOLEAN, -- whether the attribute's values are
o attr_is_trust_indicator BOOLEAN an ordered set
o attr_is_a_name BOOLEAN, -- whether the attribute's values can be
used as subjects of access control list entries
o attr_is_trust_indicator BOOLEAN -- whether the attribute's values
represent nodes in trust paths
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known (even if present as a name's attribute). known (even if present as a name's attribute).
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function outputs a name for the given name attribute, This function outputs a name for the given name attribute,
description for display to users, indicates whether the given name description for display to users, and indicates whether the
attribute's values are ordered sets, whether the given name
attribute's values are useful as the subject of an access control attribute's values are useful as the subject of an access control
list entry and/or whether the given name attribute's values are list entry and/or whether the given name attribute's values are
useful as indicators of trust (for example, whether they name PKIX useful as indicators of trust (for example, whether they name PKIX
trust anchors). trust anchors).
6.1 C-Bindings 6.1. C-Bindings
OM_uint32 gss_inquire_name_attribute( OM_uint32 gss_inquire_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name,
gss_OID attr, gss_OID attr,
gss_buffer_t attr_name, gss_buffer_t attr_name,
gss_buffer_t attr_description, gss_buffer_t attr_description,
int attr_values_ordered,
int *attr_is_a_name, int *attr_is_a_name,
int *attr_is_trust_indicator int *attr_is_trust_indicator
); );
6.2 Java Bindings
public String nameAttributeName(Oid attr)
throws GSSException
public String nameAttributeDescription(Oid attr)
throws GSSException
public boolean nameAttributeIsName(Oid attr)
throws GSSException
public boolean nameAttributeIsTrustIndicator(Oid attr)
throws GSSException
7. GSS_Display_name_ext() 7. GSS_Display_name_ext()
Inputs: Inputs:
o name NAME, o name NAME,
o display_as_name_type OBJECT IDENTIFIER o display_as_name_type OBJECT IDENTIFIER
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o display_name STRING o display_name STRING
skipping to change at page 8, line 29 skipping to change at page 8, line 39
displayed using the syntax of the given name type. displayed using the syntax of the given name type.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function displays a given name using the given name syntax, if This function displays a given name using the given name syntax, if
possible. This operation may require mapping MNs to generic name possible. This operation may require mapping MNs to generic name
syntaxes or generic name syntaxes to mechanism-specific name syntaxes or generic name syntaxes to mechanism-specific name
syntaxes; such mappings may not always be feasible and MAY be inexact syntaxes; such mappings may not always be feasible and MAY be inexact
or lossy. or lossy.
7.1 C-Bindings 7.1. C-Bindings
OM_uint32 GSS_Display_name_ext( OM_uint32 GSS_Display_name_ext(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID display_as_name_type, gss_OID display_as_name_type,
gss_buffer_t display_name gss_buffer_t display_name
); );
7.2 Java Bindings
public String displayExtended(Oid display_as_name_type)
throws GSSException
8. GSS_Inquire_name() 8. GSS_Inquire_name()
Inputs: Inputs:
o name NAME o name NAME
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o name_is_MN BOOLEAN, o name_is_MN BOOLEAN,
o mn_mech OBJECT IDENTIFIER o mn_mech OBJECT IDENTIFIER,
o asserted_attrs SET OF OBJECT IDENTIFIER o asserted_attrs SET OF OBJECT IDENTIFIER,
o authenticated_attrs SET OF OBJECT IDENTIFIER o authenticated_attrs SET OF OBJECT IDENTIFIER,
o critical_attrs SET OF OBJECT IDENTIFIER o critical_attrs SET OF OBJECT IDENTIFIER,
o all_attrs SET OF OBJECT IDENTIFIER o all_attrs SET OF OBJECT IDENTIFIER,
o [NOTE: Perhaps this function should also output an indicator as to o [NOTE: Perhaps this function should also output an indicator as to
the provenance of the name, of which, in the GSS-API, there are the provenance of the name, of which, in the GSS-API, there are
three: imported, inquired from a credential, and a peer's name three: imported, inquired from a credential, and a peer's name
inquired from a security context.] inquired from a security context.]
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function outputs the sets of attributes of a name, that are This function outputs the sets of attributes of a name, that are
authenticated, asserted or critical. It also indicates if a given authenticated, asserted or critical. It also indicates if a given
NAME is an MN or not and, if it is, what mechanism it's an MN of. NAME is an MN or not and, if it is, what mechanism it's an MN of.
8.1 C-Bindings 8.1. C-Bindings
OM_uint32 gss_inquire_name( OM_uint32 gss_inquire_name(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int name_is_MN, int name_is_MN,
gss_OID *MN_mech, gss_OID *MN_mech,
gss_OID_set *authenticated, gss_OID_set *authenticated,
gss_OID_set *asserted, gss_OID_set *asserted,
gss_OID_set *critical, gss_OID_set *critical,
gss_OID_set *all_attrs gss_OID_set *all_attrs
); );
8.2 Java Bindings
public boolean isMN(boolean authenticated, boolean critical)
throws GSSException
public Oid mnMech(boolean authenticated, boolean critical)
throws GSSException
public Oid[] allAttributes(boolean authenticated, boolean critical)
throws GSSException
public Oid[] authenticatedAttributes(boolean authenticated,
boolean critical) throws GSSException
public Oid[] assertedAttributes(boolean authenticated,
boolean critical) throws GSSException
public Oid[] criticalAttributes(boolean authenticated,
boolean critical) throws GSSException
9. GSS_Get_name_attribute() 9. GSS_Get_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o attr OBJECT IDENTIFIER o attr OBJECT IDENTIFIER
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o authenticated BOOLEAN, o authenticated BOOLEAN, -- FALSE if asserted but not authenticated
by a trusted entity
o negative BOOLEAN,
o mapped BOOLEAN, o mapped BOOLEAN,
o critical BOOLEAN, o critical BOOLEAN,
o values SET OF OCTET STRING, o values SET OF OCTET STRING,
o display_values SET OF STRING o display_values SET OF STRING
Return major_status codes: Return major_status codes:
skipping to change at page 11, line 10 skipping to change at page 11, line 5
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known or set. known or set.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function outputs the value(s) associated with a given GSS name This function outputs the value(s) associated with a given GSS name
object for a given name attribute. object for a given name attribute.
9.1 C-Bindings NOTE: This function relies on the GSS-API notion of "SET OF" allowing
for order preservation; this has been discussed on the KITTEN WG
mailing list and the consensus seems to be that, indeed, that was
always the intention.
9.1. C-Bindings
The C-bindings of GSS_Get_name_attribute() requires one function call The C-bindings of GSS_Get_name_attribute() requires one function call
per-attribute value, for multi-valued name attributes. This is done per-attribute value, for multi-valued name attributes. This is done
by using a single gss_buffer_t for each value and an input/output by using a single gss_buffer_t for each value and an input/output
integer parameter to distinguish initial and subsequent calls and to integer parameter to distinguish initial and subsequent calls and to
indicate when all values have been obtained. indicate when all values have been obtained.
The 'more' input/output parameter should point to an integer variable The 'more' input/output parameter should point to an integer variable
whose value, on first call to gss_name_attribute_get() MUST be -1, whose value, on first call to gss_name_attribute_get() MUST be -1,
and whose value upon function call return will be non-zero to and whose value upon function call return will be non-zero to
indicate that additional values remain, or zero to indicate that no indicate that additional values remain, or zero to indicate that no
values remain. The caller should not modify this parameter after the values remain. The caller should not modify this parameter after the
initial call. initial call.
OM_uint32 gss_get_name_attribute( OM_uint32 gss_get_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID attr, gss_OID attr,
int *authenticated, int *authenticated,
int *negative,
int *mapped, int *mapped,
int *critical, int *critical,
gss_buffer_t value, gss_buffer_t value,
gss_buffer_t display_value, gss_buffer_t display_value,
int *more int *more
); );
9.2 Java Bindings
public byte[] getAttributeValue(Oid attr)
throws GSSException
public String getAttributeDisplayValue(Oid attr)
throws GSSException
public boolean isAttributeAuthenticated(Oid attr)
throws GSSException
public boolean isAttributeMapped(Oid attr)
throws GSSException
public boolean getAttributeCriticality(Oid attr)
throws GSSException
10. GSS_Set_name_attribute() 10. GSS_Set_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o critical BOOLEAN, o critical BOOLEAN,
o negative BOOLEAN,
o attr OBJECT IDENTIFIER, o attr OBJECT IDENTIFIER,
o values SET OF OCTET STRING o values SET OF OCTET STRING
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER o minor_status INTEGER
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
skipping to change at page 12, line 29 skipping to change at page 12, line 19
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known or could not be set. known or could not be set.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
10.1 C-Bindings NOTE: This function relies on the GSS-API notion of "SET OF" allowing
for order preservation; this has been discussed on the KITTEN WG
mailing list and the consensus seems to be that, indeed, that was
always the intention.
10.1. C-Bindings
The C-bindings of GSS_Set_name_attribute() requires one function call The C-bindings of GSS_Set_name_attribute() requires one function call
per-attribute value, for multi-valued name attributes -- each call per-attribute value, for multi-valued name attributes -- each call
adds one value. To replace an attribute's every value delete the adds one value. To replace an attribute's every value delete the
attribute's values first with GSS_Delete_name_attribute(). attribute's values first with GSS_Delete_name_attribute().
OM_uint32 gss_set_name_attribute( OM_uint32 gss_set_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int critical, int critical,
int negative,
gss_OID attr, gss_OID attr,
gss_buffer_t value gss_buffer_t value
); );
10.2 Java Bindings
The Java-bindings of GSS_Set_name_attribute() requires one function
call per-attribute value, for multi-valued name attributes -- each
call adds one value. To replace an attribute's every value delete
the attribute's values first with GSS_Delete_name_attribute().
public abstract setAttribute(Oid attr, boolean critical,
byte[] value)
throws GSSException
11. GSS_Delete_name_attribute() 11. GSS_Delete_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o attr OBJECT IDENTIFIER, o attr OBJECT IDENTIFIER,
Outputs: Outputs:
skipping to change at page 13, line 34 skipping to change at page 13, line 18
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known. known.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
11.1 C-Bindings Deletion of negative authenticated attributes from NAME objects MUST
NOT be allowed. [Do we need a new major status code for "permission
denied"?]
11.1. C-Bindings
OM_uint32 gss_delete_name_attribute( OM_uint32 gss_delete_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID attr gss_OID attr
); );
11.2 Java Bindings
public abstract deleteAttribute(Oid attr, boolean critical)
throws GSSException
12. GSS_Export_name_composite() 12. GSS_Export_name_composite()
Inputs: Inputs:
o name NAME o name NAME
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
skipping to change at page 14, line 35 skipping to change at page 14, line 15
This function outputs a token which can be imported with This function outputs a token which can be imported with
GSS_Import_name(), using GSS_C_NT_COMPOSITE_EXPORT as the name type GSS_Import_name(), using GSS_C_NT_COMPOSITE_EXPORT as the name type
and which preserves any name attribute information associated with and which preserves any name attribute information associated with
the input name (which GSS_Export_name() may well not). The token the input name (which GSS_Export_name() may well not). The token
format is no specified here as this facility is intended for inter- format is no specified here as this facility is intended for inter-
process communication only; however, all such tokens MUST start with process communication only; however, all such tokens MUST start with
a two-octet token ID, hex 04 02, in network byte order. a two-octet token ID, hex 04 02, in network byte order.
The OID for GSS_C_NT_COMPOSITE_EXPORT is <TBD>. The OID for GSS_C_NT_COMPOSITE_EXPORT is <TBD>.
12.1 C-Bindings 12.1. C-Bindings
OM_uint32 gss_export_name_composite( OM_uint32 gss_export_name_composite(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_buffer_t exp_composite_name gss_buffer_t exp_composite_name
); );
12.2 Java Bindings
public byte[] exportComposite()
throws GSSException
13. GSS_Map_name_to_any() 13. GSS_Map_name_to_any()
Inputs: Inputs:
o name NAME, o name NAME,
o authenticated BOOLEAN, -- if TRUE no data will be output unless it o authenticated BOOLEAN, -- if TRUE no data will be output unless it
is authenticated is authenticated
o type_id OBJECT IDENTIFIER o type_id OBJECT IDENTIFIER
Outputs: Outputs:
skipping to change at page 15, line 37 skipping to change at page 15, line 13
information. information.
o GSS_S_FAILURE indicates a general error. The minor status code o GSS_S_FAILURE indicates a general error. The minor status code
may provide additional information. may provide additional information.
Whereas name attribute's values are encoded in some network Whereas name attribute's values are encoded in some network
representation applications often require native, language- and/or representation applications often require native, language- and/or
platform-specific data types. This function provides access to such platform-specific data types. This function provides access to such
types. types.
13.1 C-Bindings 13.1. C-Bindings
struct gss_any;
typedef struct gss_any *gss_any_t; typedef struct gss_any *gss_any_t;
OM_uint32 gss_map_name_to_any( OM_uint32 gss_map_name_to_any(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int authenticated, int authenticated,
gss_OID type_id, gss_OID type_id,
gss_any_t output gss_any_t output
); );
13.2 Java Bindings Note the new C bindings type, gss_any_t. We define it as a pointer
to an incompletely declared struct.
...
14. GSS_Release_any_name_mapping() 14. GSS_Release_any_name_mapping()
Inputs: Inputs:
o name NAME, o name NAME,
o type_id OBJECT IDENTIFIER, o type_id OBJECT IDENTIFIER,
o input ANY DEFINED BY type_id o input ANY DEFINED BY type_id
skipping to change at page 16, line 41 skipping to change at page 16, line 13
information. information.
o GSS_S_FAILURE indicates a general error. The minor status code o GSS_S_FAILURE indicates a general error. The minor status code
may provide additional information. may provide additional information.
This function releases, if possible, the objects of language- and/or This function releases, if possible, the objects of language- and/or
platform-specific types output by GSS_Map_name_to_any(). If such platform-specific types output by GSS_Map_name_to_any(). If such
types have native release functions applications MAY use either those types have native release functions applications MAY use either those
or this function to release the given object. or this function to release the given object.
14.1 C-Bindings 14.1. C-Bindings
struct gss_any;
typedef struct gss_any *gss_any_t; typedef struct gss_any *gss_any_t;
OM_uint32 gss_release_any_name_mapping( OM_uint32 gss_release_any_name_mapping(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID type_id, gss_OID type_id,
gss_any_t *input gss_any_t *input
); );
14.2 Java Bindings
...
15. IANA Considerations 15. IANA Considerations
This document creates a namespace of GSS-API name attributes. This document creates a namespace of GSS-API name attributes.
Attributes are named by OID, so no single authority might be needed Attributes are named by OID, so no single authority might be needed
for allocation, however, in the interest of providing the community for allocation, however, in the interest of providing the community
with an authority for name attribute OID allocation and a way to find with an authority for name attribute OID allocation and a way to find
the existing set of name attributes, the IANA should establish both, the existing set of name attributes, the IANA should establish both,
a single OID off of which name attributes could be allocated, and a a single OID off of which name attributes could be allocated, and a
registry of known GSS name attributes. registry of known GSS name attributes.
skipping to change at page 18, line 5 skipping to change at page 17, line 16
given above. given above.
16. Security Considerations 16. Security Considerations
<TBA> <TBA>
[In particular, the status of a name attribute as "authenticated" vs. [In particular, the status of a name attribute as "authenticated" vs.
"asserted" requires close review, particularly with respect to PKIX "asserted" requires close review, particularly with respect to PKIX
certificate extensions.] certificate extensions.]
17. References [Also, we need to work out the security considerations of (and
possibly remove) negative attributes.]
17.1 Normative References 17. Normative References
[I-D.GSS-NAMING] [I-D.GSS-NAMING]
Hartman, S., "Desired Enhancements to GSSAPI Naming", Hartman, S., "Desired Enhancements to GSSAPI Naming",
draft-ietf-kitten-gss-naming-01.txt (work in progress), draft-ietf-kitten-gss-naming-01.txt (work in progress),
February 2005. February 2005.
[I-D.ietf-krb-wg-kerberos-clarifications] [I-D.ietf-krb-wg-kerberos-clarifications]
Neuman, C., "The Kerberos Network Authentication Service Neuman, C., "The Kerberos Network Authentication Service
(V5)", draft-ietf-krb-wg-kerberos-clarifications-07 (work (V5)", draft-ietf-krb-wg-kerberos-clarifications-07 (work
in progress), September 2004. in progress), September 2004.
skipping to change at page 18, line 36 skipping to change at page 18, line 5
Interface Version 2, Update 1", RFC 2743, January 2000. Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
[RFC3280] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet [RFC3280] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet
X.509 Public Key Infrastructure Certificate and X.509 Public Key Infrastructure Certificate and
Certificate Revocation List (CRL) Profile", RFC 3280, Certificate Revocation List (CRL) Profile", RFC 3280,
April 2002. April 2002.
17.2 Informative References
[RFC1750] Eastlake, D., Crocker, S., and J. Schiller, "Randomness
Recommendations for Security", RFC 1750, December 1994.
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism",
RFC 1964, June 1996.
Author's Address Author's Address
Nicolas Williams Nicolas Williams
Sun Microsystems Sun Microsystems
5300 Riata Trace Ct 5300 Riata Trace Ct
Austin, TX 78727 Austin, TX 78727
US US
Email: Nicolas.Williams@sun.com Email: Nicolas.Williams@sun.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 59 change blocks. 
168 lines changed or deleted 122 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/