2 .\" Copyright (C) 2003, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH GSS_PROCESS_CONTEXT_TOKEN 3GSS "Jan 15, 2003"
8 gss_process_context_token \- pass asynchronous token to security service
12 \fBcc\fR [ \fIflag\fR... ] \fIfile\fR... \fB-lgss\fR [ \fIlibrary\fR... ]
13 #include <gssapi/gssapi.h>
15 \fBOM_uint32\fR \fBgss_process_context_token\fR(\fBOM_uint32 *\fR\fIminor_status\fR,
16 \fBconst gss_ctx_id_t\fR \fIcontext_handle\fR,\fBconst gss_buffer_t\fR \fItoken_buffer\fR);
22 The \fBgss_process_context_token()\fR function provides a way to pass an
23 asynchronous token to the security service. Most context-level tokens are
24 emitted and processed synchronously by \fBgss_init_sec_context()\fR and
25 \fBgss_accept_sec_context()\fR, and the application is informed as to whether
26 further tokens are expected by the \fBGSS_C_CONTINUE_NEEDED\fR major status
27 bit. Occasionally, a mechanism might need to emit a context-level token at a
28 point when the peer entity is not expecting a token. For example, the
29 initiator's final call to \fBgss_init_sec_context()\fR may emit a token and
30 return a status of \fBGSS_S_COMPLETE\fR, but the acceptor's call to
31 \fBgss_accept_sec_context()\fR might fail. The acceptor's mechanism might want
32 to send a token containing an error indication to the initiator, but the
33 initiator is not expecting a token at this point, believing that the context is
34 fully established. \fBgss_process_context_token()\fR provides a way to pass
35 such a token to the mechanism at any time.
38 This function is provided for compatibility with the \fBGSS-API\fR version 1.
39 Because \fBgss_delete_sec_context()\fR no longer returns a valid
40 \fIoutput_token\fR to be sent to \fBgss_process_context_token()\fR,
41 applications using a newer version of the \fBGSS-API\fR do not need to rely on
46 The parameter descriptions for \fBgss_process_context_token()\fR are as
51 \fB\fIminor_status\fR\fR
54 A mechanism-specific status code.
60 \fB\fIcontext_handle\fR\fR
63 Context handle of context on which token is to be processed.
69 \fB\fItoken_buffer\fR\fR
78 \fBgss_process_context_token()\fR returns one of the following status codes:
82 \fB\fBGSS_S_COMPLETE\fR\fR
85 Successful completion.
91 \fB\fBGSS_S_DEFECTIVE_TOKEN\fR\fR
94 Indicates that consistency checks performed on the token failed.
100 \fB\fBGSS_S_NO_CONTEXT\fR\fR
103 The \fIcontext_handle\fR did not refer to a valid context.
109 \fB\fBGSS_S_FAILURE\fR\fR
112 The underlying mechanism detected an error for which no specific \fBGSS\fR
113 status code is defined. The mechanism-specific status code reported by means
114 of the \fIminor_status\fR parameter details the error condition.
120 See \fBattributes\fR(5) for descriptions of the following attributes:
128 ATTRIBUTE TYPE ATTRIBUTE VALUE
136 \fBgss_accept_sec_context\fR(3GSS), \fBgss_delete_sec_context\fR(3GSS),
137 \fBgss_init_sec_context\fR(3GSS), \fBattributes\fR(5)
140 \fISolaris Security for Developers Guide\fR