draft-ietf-kitten-gssapi-store-cred-02.txt   draft-ietf-kitten-gssapi-store-cred-03.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Intended status: Informational October 19, 2006 Intended status: Standards Track December 30, 2008
Expires: April 22, 2007 Expires: July 3, 2009
GSS-API Extension for Storing Delegated Credentials GSS-API Extension for Storing Delegated Credentials
draft-ietf-kitten-gssapi-store-cred-02.txt draft-ietf-kitten-gssapi-store-cred-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
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 April 22, 2007. This Internet-Draft will expire on July 3, 2009.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (c) 2008 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
This document defines a new function for the GSS-API which allows This document defines a new function for the GSS-API which allows
applications to store delegated (and other) credentials in the applications to store delegated (and other) credentials in the
implicit GSS-API credential store. This is needed for GSS-API implicit GSS-API credential store. This is needed for GSS-API
applications to use delegated credentials as they would use other applications to use delegated credentials as they would use other
credentials. credentials.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . 3 1. Intended Status (To Be Removed Upon Publication) . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 4
3. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 6
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Security considerations . . . . . . . . . . . . . . . . . . . 9 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Normative References . . . . . . . . . . . . . . . . . . . . . 10 7. Security considerations . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 11 8. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 12
1. Conventions used in this document 1. Intended Status (To Be Removed Upon Publication)
The intended status of this document is BCP.
2. 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 3. Introduction
The GSS-API [RFC2743] clearly assumes that credentials exist in an The GSS-API [RFC2743] clearly assumes that credentials exist in an
implicit store whence they can be acquired using GSS_Acquire_cred() implicit store whence they can be acquired using GSS_Acquire_cred()
and GSS_Add_cred() or through use of the default credential. and GSS_Add_cred() or through use of the default credential.
Multiple credential stores may exist on a given host, but only one Multiple credential stores may exist on a given host, but only one
store may be accessed by GSS_Acquire_cred() and GSS_Add_cred() at any store may be accessed by GSS_Acquire_cred() and GSS_Add_cred() at any
given time. given time.
This assumption can be seen in sections 1.1.1.2 and 1.1.1.3 of This assumption can be seen in sections 1.1.1.2 and 1.1.1.3 of
[RFC2743] as well as in section 3.5 of [RFC2744]. [RFC2743] as well as in section 3.5 of [RFC2744].
skipping to change at page 5, line 5 skipping to change at page 6, line 5
particularly onerous on Unix systems where a call to exec() to particularly onerous on Unix systems where a call to exec() to
replace the process image obliterates any delegated credentials replace the process image obliterates any delegated credentials
handle that may exist in that process. handle that may exist in that process.
In order to make delegated credentials generally as useful as In order to make delegated credentials generally as useful as
credentials that can be acquired with GSS_Acquire_cred() and credentials that can be acquired with GSS_Acquire_cred() and
GSS_Add_cred() a primitive is needed which allows storing of GSS_Add_cred() a primitive is needed which allows storing of
credentials in the implicit credential store. This primitive we call credentials in the implicit credential store. This primitive we call
"GSS_Store_cred()." "GSS_Store_cred()."
3. GSS_Store_cred() 4. GSS_Store_cred()
Inputs: Inputs:
o input_cred_handle CREDENTIAL HANDLE, -- credential to store; MUST o input_cred_handle CREDENTIAL HANDLE, -- credential to store; MUST
NOT be GSS_C_NO_CREDENTIAL NOT be GSS_C_NO_CREDENTIAL
o cred_usage INTEGER -- 0=INITIATE-AND-ACCEPT, 1=INITIATE-ONLY, o cred_usage INTEGER -- 0=INITIATE-AND-ACCEPT, 1=INITIATE-ONLY,
2=ACCEPT-ONLY 2=ACCEPT-ONLY
o desired_mech_element OBJECT IDENTIFIER, -- if GSS_C_NULL_OID then o desired_mech_element OBJECT IDENTIFIER, -- if GSS_C_NULL_OID then
skipping to change at page 7, line 5 skipping to change at page 8, line 5
Finally, if the current credential store has no default credential Finally, if the current credential store has no default credential
(that is, no credential that could be acquired for GSS_C_NO_NAME) or (that is, no credential that could be acquired for GSS_C_NO_NAME) or
if the default_cred input argument is TRUE, and the input credential if the default_cred input argument is TRUE, and the input credential
can be successfully stored, then the input credential will be can be successfully stored, then the input credential will be
available for acquisition with GSS_C_NO_NAME as the desired name available for acquisition with GSS_C_NO_NAME as the desired name
input to GSS_Acquire_cred() or GSS_Add_cred() as well as for use as input to GSS_Acquire_cred() or GSS_Add_cred() as well as for use as
GSS_C_NO_CREDENTIAL for the cred_handle inputs to GSS_Inquire_cred(), GSS_C_NO_CREDENTIAL for the cred_handle inputs to GSS_Inquire_cred(),
GSS_Inquire_cred_by_mech(), GSS_Init_sec_context() and GSS_Inquire_cred_by_mech(), GSS_Init_sec_context() and
GSS_Accept_sec_context(). GSS_Accept_sec_context().
4. C-Bindings 5. C-Bindings
The C-bindings for GSS_Store_cred() make use of types from and are The C-bindings for GSS_Store_cred() make use of types from and are
designed based on the style of the GSS-APIv2 C-Bindings [RFC2744]. designed based on the style of the GSS-APIv2 C-Bindings [RFC2744].
OM_uint32 gss_store_cred( OM_uint32 gss_store_cred(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_cred_id_t input_cred_handle, gss_cred_id_t input_cred_handle,
gss_cred_usage_t cred_usage, gss_cred_usage_t cred_usage,
const gss_OID desired_mech, const gss_OID desired_mech,
OM_uint32 overwrite_cred, OM_uint32 overwrite_cred,
OM_uint32 default_cred, OM_uint32 default_cred,
gss_OID_set *elements_stored, gss_OID_set *elements_stored,
gss_cred_usage_t *cred_usage_stored) gss_cred_usage_t *cred_usage_stored)
Figure 1 Figure 1
The two boolean arguments, 'overwrite_cred' and 'default_cred' are The two boolean arguments, 'overwrite_cred' and 'default_cred' are
typed as OM_uint32; 0 corresponds to FALSE, non-zero values typed as OM_uint32; 0 corresponds to FALSE, non-zero values
correspond to TRUE. correspond to TRUE.
5. Examples 6. Examples
The intended usage of GSS_Store_cred() is to make delegated The intended usage of GSS_Store_cred() is to make delegated
credentials available to child processes of GSS-API acceptor credentials available to child processes of GSS-API acceptor
applications. Example pseudo-code: applications. Example pseudo-code:
/* /*
* <GSS_Accept_sec_context() loop resulting in GSS_S_COMPLETE, * <GSS_Accept_sec_context() loop resulting in GSS_S_COMPLETE,
* an initiator name (hereafter, "src_name") and a delegated * an initiator name (hereafter, "src_name") and a delegated
* credential handle (hereafter "deleg_cred").> * credential handle (hereafter "deleg_cred").>
* *
skipping to change at page 9, line 5 skipping to change at page 10, line 5
*/ */
if (change_user_context(requested_username)) if (change_user_context(requested_username))
(void) gss_store_creds(&minor_status, deleg_cred, (void) gss_store_creds(&minor_status, deleg_cred,
GSS_C_INITIATE, actual_mech, GSS_C_INITIATE, actual_mech,
0, 1, NULL, NULL); 0, 1, NULL, NULL);
} }
else ... else ...
} }
else ... else ...
6. Security considerations 7. Security considerations
Acceptor applications MUST only store delegated credentials into Acceptor applications MUST only store delegated credentials into
appropriate credential stores and only after proper authorization of appropriate credential stores and only after proper authorization of
the authenticated initiator principal to the requested service(s). the authenticated initiator principal to the requested service(s).
Acceptor applications that have no use for delegated credentials MUST Acceptor applications that have no use for delegated credentials MUST
release them (such acceptor applications that use the GSS-API release them (such acceptor applications that use the GSS-API
C-Bindings may simply provide a NULL value for the C-Bindings may simply provide a NULL value for the
delegated_cred_handle argument to gss_accept_sec_context()). delegated_cred_handle argument to gss_accept_sec_context()).
7. Normative References 8. 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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
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.
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
Full Copyright Statement
Copyright (C) The Internet Society (2006).
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.
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.
Intellectual Property
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 14 change blocks. 
25 lines changed or deleted 35 lines changed or added

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