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.
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 schemeThere must also be a reportscheme entry in the /etc/services file:
#service name port number/transport # reportscheme 2768/tcpwith the following entry in /etc/hosts:
#host address host name # 220.127.116.11 elvisA 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 schemeIn this case, the entry in the /etc/net/ticots/services file will be:
#service name service port # reportscheme reportschemeThe entry in the /etc/net/ticots/hosts file will be:
#machine addr machine name # elvis elvis