1gss_delete_sec_coGnetneexrti(c3GSSeSc)urity Services API Libragrsys_Fduenlcettieo_nssec_context(3GSS)
2
3
4
6 gss_delete_sec_context - delete a GSS-API security context
7
9 cc [ flag... ] file... -lgss [ library... ]
10 #include <gssapi/gssapi.h>
11
12 OM_uint32 gss_delete_sec_context(OM_uint32 *minor_status,
13 gss_ctx_id_t *context_handle,gss_buffer_t output_token);
14
15
17 Use the gss_delete_sec_context() function to delete a security context.
18 The gss_delete_sec_context() function will delete the local data struc‐
19 tures associated with the specified security context. You may not
20 obtain further security services that use the context specified by con‐
21 text_handle.
22
23
24 In addition to deleting established security contexts,
25 gss_delete_sec_context() will delete any half-built security contexts
26 that result from incomplete sequences of calls to gss_init_sec_con‐
27 text(3GSS) and gss_accept_sec_context(3GSS).
28
29
30 The Solaris implementation of the GSS-API retains the output_token
31 parameter for compatibility with version 1 of the GSS-API. Both peer
32 applications should invoke gss_delete_sec_context(), passing the value
33 GSS_C_NO_BUFFER to the output_token parameter; this indicates that no
34 token is required. If the application passes a valid buffer to
35 gss_delete_sec_context(), it will return a zero-length token, indicat‐
36 ing that no token should be transferred by the application.
37
39 The parameter descriptions for gss_delete_sec_context() follow:
40
41 minor_status A mechanism specific status code.
42
43
44 context_handle Context handle identifying specific context to
45 delete. After deleting the context, the GSS-API will
46 set context_handle to GSS_C_NO_CONTEXT.
47
48
49 output_token A token to be sent to remote applications that
50 instructs them to delete the context.
51
52
54 gss_delete_sec_context() may return the following status codes:
55
56 GSS_S_COMPLETE Successful completion.
57
58
59 GSS_S_NO_CONTEXT No valid context was supplied.
60
61
62 GSS_S_FAILURE The underlying mechanism detected an error for
63 which no specific GSS status code is defined. The
64 mechanism-specific status code reported by means of
65 the minor_status parameter details the error condi‐
66 tion.
67
68
70 See attributes(5) for descriptions of the following attributes:
71
72
73
74
75 ┌─────────────────────────────┬─────────────────────────────┐
76 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
77 ├─────────────────────────────┼─────────────────────────────┤
78 │Availability │SUNWgss (32-bit) │
79 ├─────────────────────────────┼─────────────────────────────┤
80 │ │SUNWgssx (64-bit) │
81 ├─────────────────────────────┼─────────────────────────────┤
82 │MT-Level │Safe │
83 └─────────────────────────────┴─────────────────────────────┘
84
86 gss_accept_sec_context(3GSS), gss_init_sec_context(3GSS), attributes(5)
87
88
89 Solaris Security for Developers Guide
90
91
92
93SunOS 5.11 15 jan 2003 gss_delete_sec_context(3GSS)