1rpc_gss_set_callback(3NNeStLw)orking Services Library Funcrtpico_ngsss_set_callback(3NSL)
2
6 rpc_gss_set_callback - specify callback for context
7
9 #include <rpc/rpcsec_gss.h>
10 bool_t rpc_gss_set_callback(struct rpc_gss_callback_t *cb);
12
15 A server may want to specify a callback routine so that it knows when a
16 context gets first used. This user-defined callback may be specified
17 through the rpc_gss_set_callback() routine. The callback routine is
18 invoked the first time a context is used for data exchanges, after the
19 context is established for the specified program and version.
20 The user-defined callback routine should take the following form:
23 bool_t callback(struct svc_req *req, gss_cred_id_t deleg,
25 gss_ctx_id_t gss_context, rpc_gss_lock_t *lock, void **cookie);
26
29 rpc_gss_set_callback() takes one argument: a pointer to a
30 rpc_gss_callback_t structure. This structure contains the RPC program
31 and version number as well as a pointer to a user-defined callback()
32 routine. (For a description of rpc_gss_callback_t and other RPCSEC_GSS
33 data types, see the rpcsec_gss(3NSL) man page.)
34 The user-defined callback() routine itself takes the following argu‐
37 ments:
38 req Pointer to the received service request. svc_req is
40 an RPC structure containing information on the context
41 of an RPC invocation, such as program, version, and
42 transport information.
43 deleg Delegated credentials, if any. (See NOTES, below.)
46 gss_context GSS context (allows server to do GSS operations on the
49 context to test for acceptance criteria). See NOTES,
50 below.
51 lock This parameter is used to enforce a particular QOP and
54 service for a session. This parameter points to a RPC‐
55 SEC_GSS rpc_gss_lock_t structure. When the callback is
56 invoked, the rpc_gss_lock_t.locked field is set to
57 TRUE, thus locking the context. A locked context will
58 reject all requests having different values for QOP or
59 service than those specified by the raw_cred field of
60 the rpc_gss_lock_t structure.
61 cookie A four-byte quantity that an application may use in any
64 manner it wants to — RPC does not interpret it. (For
65 example, the cookie could be a pointer or index to a
66 structure that represents a context initiator.) The
67 cookie is returned, along with the caller's creden‐
68 tials, with each invocation of rpc_gss_getcred().
69
72 rpc_gss_set_callback() returns TRUE if the use of the context is
73 accepted; false otherwise.
74
76 See attributes(5) for descriptions of the following attributes:
77 ┌─────────────────────────────┬─────────────────────────────┐
82 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
83 ├─────────────────────────────┼─────────────────────────────┤
84 │MT-Level │MT-Safe │
85 ├─────────────────────────────┼─────────────────────────────┤
86 │Availability │SUNWrsg (32-bit) │
87 ├─────────────────────────────┼─────────────────────────────┤
88 │ │SUNWrsgx (64-bit) │
89 └─────────────────────────────┴─────────────────────────────┘
90
92 rpc(3NSL), rpc_gss_getcred(3NSL), rpcsec_gss(3NSL), attributes(5)
93 ONC+ Developer's Guide
96 Linn, J. RFC 2078, Generic Security Service Application Program Inter‐
99 face, Version 2. Network Working Group. January 1997.
100
102 If a server does not specify a callback, all incoming contexts will be
103 accepted.
104 Because the GSS-API is not currently exposed, the deleg and gss_context
107 arguments are mentioned for informational purposes only, and the user-
108 defined callback function may choose to do nothing with them.
109SunOS 5.11 5 Feb 2002 rpc_gss_set_callback(3NSL)