GSS_CANONICALIZE_NAME(3) Programmer's Manual GSS_CANONICALIZE_NAME(3)NAMEgss_canonicalize_name — Convert an internal name to an MN
const gss_name_t input_name, const gss_OID mech_type,
Generate a canonical mechanism name (MN) from an arbitrary internal name.
The mechanism name is the name that would be returned to a context accep‐
tor on successful authentication of a context where the initiator used
the input_name in a successful call to gss_acquire_cred(), specifying an
OID set containing mech_type as its only member, followed by a call to
gss_init_sec_context(), specifying mech_type as the authentication mecha‐
minor_status Mechanism specific status code.
input_name The name for which a canonical form is desired.
mech_type The authentication mechanism for which the canonical form
of the name is desired. The desired mechanism must be
no default is provided.
output_name The resultant canonical name. Storage associated with this
name must be freed by the application after use with a call
The identified mechanism is not supported.
The provided internal name contains no elements that could
be processed by the specified mechanism.
The provided internal name was ill-formed.
SEE ALSOgss_acquire_cred(3), gss_init_sec_context(3), gss_release_name(3)STANDARDS
RFC 2743 Generic Security Service Application Program Interface Ver‐
sion 2, Update 1
RFC 2744 Generic Security Service API Version 2 : C-bindings
The gss_canonicalize_name function first appeared in FreeBSD 7.0.
John Wray, Iris Associates
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to oth‐
ers, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and dis‐
tributed, in whole or in part, without restriction of any kind, provided
that the above copyright notice and this paragraph are included on all
such copies and derivative works. However, this document itself may not
be modified in any way, such as by removing the copyright notice or ref‐
erences to the Internet Society or other Internet organizations, except
as needed for the purpose of developing Internet standards in which case
the procedures for copyrights defined in the Internet Standards process
must be followed, or as required to translate it into languages other
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FIT‐
NESS FOR A PARTICULAR PURPOSE.
BSD January 26, 2010 BSD