rpc_clnt_auth(3N) rpc_clnt_auth(3N)
NAME
rpc_clnt_auth: auth_destroy(), authnone_create(), authsys_create(), authsys_create_default() - library routines for client side remote pro-
cedure call authentication
SYNOPSIS
DESCRIPTION
These routines are part of the RPC library that allows C language programs to make procedure calls on other machines across the network,
with desired authentication.
These routines are normally called after creating the handle. The field of the structure should be initialized by the structure returned
by some of the following routines. The client's authentication information is passed to the server when the RPC call is made.
Only the and the style of authentication is discussed here. For the style authentication, please refer to secure_rpc(3N).
The and style of authentication are safe in multithreaded applications.
The HP-UX implementation of RPC only supports the X/Open Transport Interface (XTI). Applications that are written using the Transport
Layer Interface (TLI) and wish to use RPC, must convert their application to XTI.
Routines
The following routines require that the header be included (see rpc(3N) for the definition of the data structure).
A function macro that destroys the authentication
information associated with auth. Destruction usually involves deallocation of private data structures. The use of auth is unde-
fined after calling
Create and return an RPC
authentication handle that passes nonusable authentication information with each remote procedure call. This is the default authen-
tication used by RPC.
Create and return an RPC authentication handle that contains
authentication information. The parameter host is the name of the machine on which the information was created; uid is the user's
user ID; gid is the user's current group ID; len and aup_gids refer to a counted array of groups to which the user belongs.
Call with the appropriate parameters.
MULTITHREAD USAGE
Thread Safe: Yes
Cancel Safe: Yes
Fork Safe: No
Async-cancel Safe: No
Async-signal Safe: No
These functions can be called safely in a multithreaded environment. They may be cancellation points in that they call functions that are
cancel points.
In a multithreaded environment, these functions are not safe to be called by a child process after and before These functions should not be
called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.
SEE ALSO
rpc(3N), rpc_clnt_calls(3N), rpc_clnt_create(3N), secure_rpc(3N).
rpc_clnt_auth(3N)
