Administering the connection server

The reportscheme service

reportscheme(1Mbnu) is a network service invoked by the connection server to determine what authentication scheme is associated with a given service on the server machine. If the server is to enforce authentication scheme invocation, a reportscheme line must appear in the port monitor administrative file for every port monitor that offers network services. If the reportscheme service is not entered in a port monitor's administrative file, applications on client machines cannot successfully query scheme information and will assume a NULL authentication scheme is associated with the service to which they are trying to connect.

NOTE: The reportscheme entry itself must not have an authentication scheme associated with it.

The following is a sample reportscheme entry in the port monitor administrative file /etc/saf/tcp/_pmtab.

reportscheme::root:reserved:reserved::\x00020AD0C00B02510000000000000000::c::
/usr/sbin/reportscheme#reportscheme service - no authentication scheme

There must also be a reportscheme entry in the /etc/services file:

   #service name      port number/transport
   #
   reportscheme       2768/tcp

with the following entry in /etc/hosts:

   #host address      host name
   #
   192.11.2.81        elvis

A reportscheme entry in the ticots port monitor administrative file /etc/saf/ticots/_pmtab will look like this:

   reportscheme::root:reserved:reserved::elvis.reportscheme::c::/usr/sbin/reportscheme
   #reportscheme service - no authentication scheme

In this case, the entry in the /etc/net/ticots/services file will be:

   #service name      service port
   #
   reportscheme       reportscheme

The entry in the /etc/net/ticots/hosts file will be:

   #machine addr      machine name
   #
   elvis              elvis