draft-ietf-kitten-gssapi-store-cred-01.txt   draft-ietf-kitten-gssapi-store-cred-02.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: April 19, 2006 October 16, 2005 Intended status: Informational October 19, 2006
Expires: April 22, 2007
GSS-API Extension for Storing Delegated Credentials GSS-API Extension for Storing Delegated Credentials
draft-ietf-kitten-gssapi-store-cred-01.txt draft-ietf-kitten-gssapi-store-cred-02.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 33 skipping to change at page 1, line 34
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 19, 2006. This Internet-Draft will expire on April 22, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
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. Conventions used in this document . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 5 3. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 5
4. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Security considerations . . . . . . . . . . . . . . . . . . . 9 6. Security considerations . . . . . . . . . . . . . . . . . . . 9
7. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . 12
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
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].
Note to the RFC editor: please remove this note before publication.]
Applications may be able to change the credential store from which Applications may be able to change the credential store from which
credentials can be acquired, either by changing user contexts (where credentials can be acquired, either by changing user contexts (where
the applications have the privilege to do so) or by other means the applications have the privilege to do so) or by other means
(where a user may have multiple credential stores). (where a user may have multiple credential stores).
Some GSS-API acceptor applications always change user contexts, after Some GSS-API acceptor applications always change user contexts, after
accepting a GSS-API security context and making appropriate accepting a GSS-API security context and making appropriate
authorization checks, to the user context corresponding to the authorization checks, to the user context corresponding to the
initiator principal name or to a context requested by the initiator. initiator principal name or to a context requested by the initiator.
The means by which credential stores are managed are generally beyond The means by which credential stores are managed are generally beyond
the scope of the GSS-API. the scope of the GSS-API.
In the case of delegated credential handles however, such credentials In the case of delegated credential handles however, such credentials
do not exist in the acceptor's credential store or in the credential do not exist in the acceptor's credential store or in the credential
stores of the user contexts to which the acceptor application might stores of the user contexts to which the acceptor application might
change - which is precisely the raison d'etre of credential change. The GSS-API provides no mechanism by which delegated
delegation. But the GSS-API provides no mechanism by which delegated
credential handles can be made available for acquisition through credential handles can be made available for acquisition through
GSS_Acquire_cred()/GSS_Add_cred(). The GSS-API also does not provide GSS_Acquire_cred()/GSS_Add_cred(). The GSS-API also does not provide
any credential import/export interfaces like the GSS-API context any credential import/export interfaces like the GSS-API context
import/export interfaces. import/export interfaces.
Thus acceptors are limited to making only direct use of delegated Thus acceptors are limited to making only direct use of delegated
credential handles and only with GSS_Init_sec_context(), credential handles and only with GSS_Init_sec_context(),
GSS_Inquire_cred*() and GSS_Release_cred(). This limitation is GSS_Inquire_cred*() and GSS_Release_cred(). This limitation is
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 the delegated credentials replace the process image obliterates any delegated credentials
handle. 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() 3. GSS_Store_cred()
Inputs: Inputs:
skipping to change at page 7, line 12 skipping to change at page 7, line 12
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 4. 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, 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
skipping to change at page 8, line 26 skipping to change at page 8, line 26
* <"requested_username" is a username derived from the * <"requested_username" is a username derived from the
* initiator name or explicitly requested by the initiator * initiator name or explicitly requested by the initiator
* application.> * application.>
*/ */
... ...
if (authorize_gss_client(src_name, requested_username)) { if (authorize_gss_client(src_name, requested_username)) {
/* /*
* For Unix-type platforms this may mean calling setuid() and * For Unix-type platforms this may mean calling setuid() and
* it may or may not also mean setting/unsetting such * it may or may not also mean setting/unsetting such
* environment variables as KRB5CCNAME and what not. * environment variables as KRB5CCNAME and what not -- all
* OS-specific details.
*/ */
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 ...
skipping to change at page 9, line 16 skipping to change at page 10, line 5
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 7. 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
Intellectual Property Statement 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 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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 11, line 29 skipping to change at page 12, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. 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 (2005). 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 Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 14 change blocks. 
33 lines changed or deleted 32 lines changed or added

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