freebsd man page for gss_canonicalize_name

Query: gss_canonicalize_name

OS: freebsd

Section: 3

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

GSS_CANONICALIZE_NAME(3)					Programmer's Manual					  GSS_CANONICALIZE_NAME(3)

NAME
gss_canonicalize_name -- Convert an internal name to an MN
SYNOPSIS
#include <gssapi/gssapi.h> OM_uint32 gss_canonicalize_name(OM_uint32 *minor_status, const gss_name_t input_name, const gss_OID mech_type, gss_name_t *output_name);
DESCRIPTION
Generate a canonical mechanism name (MN) from an arbitrary internal name. The mechanism name is the name that would be returned to a context acceptor on successful authentication of a context where the initiator used the input_name in a successful call to gss_acquire_cred(), speci- fying an OID set containing mech_type as its only member, followed by a call to gss_init_sec_context(), specifying mech_type as the authenti- cation mechanism.
PARAMETERS
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 specified explicitly; 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 to gss_release_name().
RETURN VALUES
GSS_S_COMPLETE Successful completion. GSS_S_BAD_MECH The identified mechanism is not supported. GSS_S_BAD_NAMETYPE The provided internal name contains no elements that could be processed by the specified mechanism. GSS_S_BAD_NAME The provided internal name was ill-formed.
SEE ALSO
gss_acquire_cred(3), gss_init_sec_context(3), gss_release_name(3)
STANDARDS
RFC 2743 Generic Security Service Application Program Interface Version 2, Update 1 RFC 2744 Generic Security Service API Version 2 : C-bindings
HISTORY
The gss_canonicalize_name function first appeared in FreeBSD 7.0.
AUTHORS
John Wray, Iris Associates
COPYRIGHT
Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, pro- vided 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 references to the Internet Society or other Internet organiza- tions, 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 than English. 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 FITNESS FOR A PARTICULAR PURPOSE.
BSD
January 26, 2010 BSD
Related Man Pages
gss_inquire_mechs_for_name(3) - freebsd
gss_canonicalize_name(3gss) - opensolaris
gss_context_time(3) - freebsd
gss_canonicalize_name(3) - freebsd
gss_duplicate_name(3) - freebsd
Similar Topics in the Unix Linux Community
Scripts without shebang
Memory Leaks
Is UNIX an open source OS ?
Reason for no directory creation date
Is it safe to install x86 Solaris 10 U6 after installed-Linux-and-FreeBSD?