1gss_canonicalize_Gneanmeer(i3cGSSSe)curity Services API LibrargyssF_ucnacntoinoincsalize_name(3GSS)
2
3
4

NAME

6       gss_canonicalize_name - convert an internal name to a mechanism name
7

SYNOPSIS

9       cc [flag ...] file... -lgss [library ...]
10       #include <gssapi/gssapi.h>
11
12       OM_uint32 gss_canonicalize_name(OM_uint32 *minor_status,
13            const gss_name_t input_name,const gss_OID mech_type,
14            gss_name_t *output_name);
15
16

DESCRIPTION

18       The  gss_canonicalize_name()  function  generates a canonical mechanism
19       name from an arbitrary internal name.  The mechanism name is  the  name
20       that  would be returned to a context acceptor on successful authentica‐
21       tion of a context where the initiator used the input_name in a success‐
22       ful  call  to  gss_acquire_cred(3GSS), specifying an OID set containing
23       mech_type as its only member, followed by a call  to  gss_init_sec_con‐
24       text(3GSS), specifying mech_type as the authentication mechanism.
25

PARAMETERS

27       The parameter descriptions for gss_canonicalize_name() follow:
28
29       minor_status    Mechanism-specific status code.
30
31
32       input_name      The name for which a canonical form is desired.
33
34
35       mech_type       The  authentication  mechanism  for which the canonical
36                       form of the name is  desired.   The  desired  mechanism
37                       must be specified explicitly; no default is provided.
38
39
40       output_name     The  resultant canonical name.  Storage associated with
41                       this name must be freed by the  application  after  use
42                       with a call to gss_release_name(3GSS).
43
44

ERRORS

46       The gss_canonicalize_name() function may return the status codes:
47
48       GSS_S_COMPLETE        Successful completion.
49
50
51       GSS_S_BAD_MECH        The identified mechanism is not supported.
52
53
54       GSS_S_BAD_NAMETYPE    The  provided  internal name contains no elements
55                             that could be processed by the  specified  mecha‐
56                             nism.
57
58
59       GSS_S_BAD_NAME        The provided internal name was ill-formed.
60
61
62       GSS_S_FAILURE         The  underlying  mechanism  detected an error for
63                             which no specific GSS  status  code  is  defined.
64                             The  mechanism-specific  status  code reported by
65                             means of the minor_status parameter  details  the
66                             error condition.
67
68

ATTRIBUTES

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

SEE ALSO

86       gss_acquire_cred(3GSS),                     gss_init_sec_context(3GSS),
87       gss_release_name(3GSS), attributes(5)
88
89
90       Solaris Security for Developers Guide
91
92
93
94SunOS 5.11                        14 Jan 2003      gss_canonicalize_name(3GSS)
Impressum