RSC/MP Programming Manual

Access Control Server A Sample ACS for the NonStop Host
HOST_ACS_NAME Use this option to supply the name of the ACS object in
the TDP. However, this option is ignored if the TERM
object in the TDP is configured to use an ACS object.
PASSWORD Each session can have a unique password specified by
the client application in an RscSetOption function call.
USER_ID This option is case sensitive. Each session can have a
unique USER_ID specified by the client application in
an RscSetOption function call.
A Sample ACS for the NonStop Host
These steps describe an approach to developing an ACS based on a code sample
included with the RSC/MP deliverables. Note that this is an example and the steps
outlined are only suggestions; the mechanisms used by a user-written ACS to validate
users are totally dependent on the needs of the user.
1. On the NonStop, locate the RSC/MP sample source file SAMPACSC and the
corresponding executable, SAMPACS.
2. Create an edit file such as RSCUSERS, and add the list of valid user IDs and
passwords into this file. These values must match the values in the options that are
used on the client workstations that are using this TDP and ACS. The file has this
format:
user_id password
user_id password
…
The ACS can also use this data from a key-sequenced file.
The ACS application checks the data in this file when the TDP receives an
RscBeginSession request.
3. Create an edit file such as RSCSRVRS, and add the list of authorized servers into
this file in this format:
n1n2 processname serverclass
n1 One of these decimal values describing the type of process
on the NonStop host:
1 – A PATHMON process and a specific server class under
that process.
2 – A PATHMON process including all server classes
running under that process.
3 – A stand-alone process.
HP NonStop Remote Server Call (RSC/MP) Programming Manual — 522360-006
9- 5