1gss_inquire_mechsG_efnoerr_incamSee(c3uGrSiSt)y Services API Lgisbsr_airnyquFiurnec_tmieocnhss_for_name(3GSS)
2
3
4
6 gss_inquire_mechs_for_name - list mechanisms that support the specified
7 name-type
8
10 cc [flag ...] file... -lgss [library ...]
11 #include <gssapi/gssapi.h>
12
13 OM_uint32 gss_inquire_mechs_for_name(OM_uint32 *minor_status,
14 const gss_name_t input_name,gss_OID_set *mech_types);
15
16
18 The gss_inquire_mechs_for_name() function returns the set of mechanisms
19 supported by the GSS-API that may be able to process the specified
20 name. Each mechanism returned will recognize at least one element
21 within the internal name.
22
23
24 Some implementations of the GSS-API may perform this test by checking
25 nametype information contained within the passed name and registration
26 information provided by individual mechanisms. This means that the
27 mech_types set returned by the function may indicate that a particular
28 mechanism will understand the name, when in fact the mechanism would
29 refuse to accept the name as input to gss_canonicalize_name(3GSS),
30 gss_init_sec_context(3GSS), gss_acquire_cred(3GSS), or
31 gss_add_cred(3GSS), due to some property of the name itself rather than
32 the name-type. Therefore, this function should be used only as a pre-
33 filter for a call to a subsequent mechanism-specific function.
34
36 The parameter descriptions for gss_inquire_mechs_for_name() follow in
37 alphabetical order:
38
39 minor_status Mechanism-specific status code.
40
41
42 input_name The name to which the inquiry relates.
43
44
45 mech_types Set of mechanisms that may support the specified name.
46 The returned OID set must be freed by the caller after
47 use with a call to gss_release_oid_set(3GSS).
48
49
51 The gss_inquire_mechs_for_name() function may return the following sta‐
52 tus codes:
53
54 GSS_S_COMPLETE Successful completion.
55
56
57 GSS_S_BAD_NAME The input_name parameter was ill-formed.
58
59
60 GSS_S_BAD_NAMETYPE The input_name parameter contained an invalid or
61 unsupported type of name.
62
63
64 GSS_S_FAILURE The underlying mechanism detected an error for
65 which no specific GSS status code is defined.
66 The mechanism-specific status code reported by
67 means of the minor_status parameter details the
68 error condition.
69
70
72 See attributes(5) for descriptions of the following attributes:
73
74
75
76
77 ┌─────────────────────────────┬─────────────────────────────┐
78 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
79 ├─────────────────────────────┼─────────────────────────────┤
80 │Availability │SUNWgss (32-bit) │
81 ├─────────────────────────────┼─────────────────────────────┤
82 │ │SUNWgssx (64-bit) │
83 ├─────────────────────────────┼─────────────────────────────┤
84 │MT-Level │Safe │
85 └─────────────────────────────┴─────────────────────────────┘
86
88 gss_acquire_cred(3GSS), gss_add_cred(3GSS), gss_canonical‐
89 ize_name(3GSS), gss_init_sec_context(3GSS), gss_release_oid_set(3GSS),
90 attributes(5)
91
92
93 Solaris Security for Developers Guide
94
95
96
97SunOS 5.11 15 Jan 2003 gss_inquire_mechs_for_name(3GSS)