1 '\" te
   2 .\" Copyright (C) 2002, Sun Microsystems, Inc. All Rights Reserved
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH RPC_GSS_GET_PRINCIPAL_NAME 3NSL "Feb 5, 2002"
   7 .SH NAME
   8 rpc_gss_get_principal_name \- Get principal names at server
   9 .SH SYNOPSIS
  10 .LP
  11 .nf
  12 #include <rpc/rpcsec_gss.h>
  13 
  14 \fBbool_t\fR \fBrpc_gss_get_principal_name\fR(\fBrpc_gss_principal_\fR \fI*principal\fR,
  15      \fBchar\fR \fI*mech\fR, \fBchar\fR \fI*name\fR, \fBchar\fR \fI*node\fR, \fBchar\fR \fI*domain\fR);
  16 .fi
  17 
  18 .SH DESCRIPTION
  19 .sp
  20 .LP
  21 Servers need to be able to operate on a client's principal name. Such a name is
  22 stored by the server as a  \fBrpc_gss_principal_t\fR structure, an opaque byte
  23 string which can be used either directly in access control lists or as database
  24 indices which can be used to look up a UNIX credential. A server may, for
  25 example, need to compare a principal name it has received with the principal
  26 name of a known entity, and to do that, it must be able to generate
  27 \fBrpc_gss_principal_t\fR structures from known entities.
  28 .sp
  29 .LP
  30 \fBrpc_gss_get_principal_name()\fR takes as input a security mechanism, a
  31 pointer to a \fBrpc_gss_principal_t\fR structure, and several parameters which
  32 uniquely identify an entity on a network: a user or service name, a node name,
  33 and a domain name.  From these parameters it constructs a unique,
  34 mechanism-dependent principal name of the \fBrpc_gss_principal_t\fR structure

   1 '\" te
   2 .\" Copyright (C) 2002, Sun Microsystems, Inc. All Rights Reserved
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH RPC_GSS_GET_PRINCIPAL_NAME 3NSL "Jun 17, 2014"
   7 .SH NAME
   8 rpc_gss_get_principal_name \- Get principal names at server
   9 .SH SYNOPSIS
  10 .LP
  11 .nf
  12 #include <rpc/rpcsec_gss.h>
  13 
  14 \fBbool_t\fR \fBrpc_gss_get_principal_name\fR(\fBrpc_gss_principal_t\fR \fI*principal\fR,
  15      \fBchar\fR \fI*mech\fR, \fBchar\fR \fI*name\fR, \fBchar\fR \fI*node\fR, \fBchar\fR \fI*domain\fR);
  16 .fi
  17 
  18 .SH DESCRIPTION
  19 .sp
  20 .LP
  21 Servers need to be able to operate on a client's principal name. Such a name is
  22 stored by the server as a  \fBrpc_gss_principal_t\fR structure, an opaque byte
  23 string which can be used either directly in access control lists or as database
  24 indices which can be used to look up a UNIX credential. A server may, for
  25 example, need to compare a principal name it has received with the principal
  26 name of a known entity, and to do that, it must be able to generate
  27 \fBrpc_gss_principal_t\fR structures from known entities.
  28 .sp
  29 .LP
  30 \fBrpc_gss_get_principal_name()\fR takes as input a security mechanism, a
  31 pointer to a \fBrpc_gss_principal_t\fR structure, and several parameters which
  32 uniquely identify an entity on a network: a user or service name, a node name,
  33 and a domain name.  From these parameters it constructs a unique,
  34 mechanism-dependent principal name of the \fBrpc_gss_principal_t\fR structure