Connection server components
The connection server is made up of the following components:
In addition, the connection server may make use of
the Service Access Facility's (SAF) administrative command,
to install authentication schemes.
An application interface to the standing server.
The interface consists of
library routines that make
the connection over connection-oriented networks
or using dialup connections
and an error reporting routine.
The use of the application interface routines
is described in
``The connection server''
An /etc/iaf/serve.allow file,
maintained on the client machine.
contains a list of network services
that client applications expect to use
and the acceptable authentication scheme or schemes
for each service.
This file is not needed
if client applications do not authenticate
that is, if client applications will accept
any authentication scheme imposed by server machines.
/etc/iaf/serve.allow is described in the section
``Maintaining the /etc/iaf/serve.allow file''.
An optional file,
also maintained on the client machine.
contains a list of server names,
network service names, and their aliases.
The file is described in
``Maintaining the /etc/iaf/serve.alias file''.
A non-standing network service,
that tells client machine applications
what authentication scheme to use
for a requested network service.
The reportscheme service
must exist on each port monitor
that offers network services
if the server is to enforce
authentication scheme invocation.
reportscheme is described in
``The reportscheme service'',
``The connection server'',
A connection server log file.
The application interface to the connection server
consists of the library routines
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004