1gss_process_conteGxetn_etroikcenS(e3cGuSrSi)ty Services API Ligbsrsa_rpyroFcuenscst_icoonnstext_token(3GSS)
2
3
4
6 gss_process_context_token - pass asynchronous token to security service
7
9 cc [ flag... ] file... -lgss [ library... ]
10 #include <gssapi/gssapi.h>
11
12 OM_uint32 gss_process_context_token(OM_uint32 *minor_status,
13 const gss_ctx_id_t context_handle,const gss_buffer_t token_buffer);
14
15
17 The gss_process_context_token() function provides a way to pass an
18 asynchronous token to the security service. Most context-level tokens
19 are emitted and processed synchronously by gss_init_sec_context() and
20 gss_accept_sec_context(), and the application is informed as to whether
21 further tokens are expected by the GSS_C_CONTINUE_NEEDED major status
22 bit. Occasionally, a mechanism might need to emit a context-level token
23 at a point when the peer entity is not expecting a token. For example,
24 the initiator's final call to gss_init_sec_context() may emit a token
25 and return a status of GSS_S_COMPLETE, but the acceptor's call to
26 gss_accept_sec_context() might fail. The acceptor's mechanism might
27 want to send a token containing an error indication to the initiator,
28 but the initiator is not expecting a token at this point, believing
29 that the context is fully established. gss_process_context_token() pro‐
30 vides a way to pass such a token to the mechanism at any time.
31
32
33 This function is provided for compatibility with the GSS-API version 1.
34 Because gss_delete_sec_context() no longer returns a valid output_token
35 to be sent to gss_process_context_token(), applications using a newer
36 version of the GSS-API do not need to rely on this function.
37
39 The parameter descriptions for gss_process_context_token() are as fol‐
40 lows:
41
42 minor_status A mechanism-specific status code.
43
44
45 context_handle Context handle of context on which token is to be
46 processed.
47
48
49 token_buffer Token to process.
50
51
53 gss_process_context_token() returns one of the following status codes:
54
55 GSS_S_COMPLETE Successful completion.
56
57
58 GSS_S_DEFECTIVE_TOKEN Indicates that consistency checks performed on
59 the token failed.
60
61
62 GSS_S_NO_CONTEXT The context_handle did not refer to a valid
63 context.
64
65
66 GSS_S_FAILURE The underlying mechanism detected an error for
67 which no specific GSS status code is defined.
68 The mechanism-specific status code reported by
69 means of the minor_status parameter details
70 the error condition.
71
72
74 See attributes(5) for descriptions of the following attributes:
75
76
77
78
79 ┌─────────────────────────────┬─────────────────────────────┐
80 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
81 ├─────────────────────────────┼─────────────────────────────┤
82 │Availability │SUNWgss (32-bit) │
83 ├─────────────────────────────┼─────────────────────────────┤
84 │ │SUNWgssx (64-bit) │
85 ├─────────────────────────────┼─────────────────────────────┤
86 │MT Level │Safe │
87 └─────────────────────────────┴─────────────────────────────┘
88
90 gss_accept_sec_context(3GSS), gss_delete_sec_context(3GSS),
91 gss_init_sec_context(3GSS), attributes(5)
92
93
94 Solaris Security for Developers Guide
95
96
97
98SunOS 5.11 15 Jan 2003 gss_process_context_token(3GSS)