OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-35
Using the Master Password Server
•
What will you name the authorization databases (one per server process), and where
will they reside?
•
How many master users will you define? (You need exactly one configuration
database for each master user, regardless of the number of MPS processes.)
•
What will you name the configuration databases, and where will they reside?
•
What will be the APPL name of each master user?
•
What is the MHSMGR process name?
It is often practical to assign MPS process, database, and APPL names that make it easy
to remember which databases belong to which process and which APPLs belong
together for administrative purposes. By contrast, it is usually not in the best interest of
security if the name of the master user can be easily recognized.
Once you have planned your MPS configuration, the next step is to create the
authorization database.
Create the Authorization Database
Follow these steps to create an empty authorization database large enough to support
24,800 APPLs:
1. Log on as the user who owns the MHSMGR of the OSI/MHS subsystem.
2. At a TACL prompt, load the MPSINST macro file (from the ISV) by typing:
LOAD MPSINST
Once the file is loaded, run the mps_cr_auth macro by typing:
mps_cr_auth filename
where filename specifies the fully qualified name and location of the
authorization database.
If you do not specify a filename, the macro displays a message and then exits. If
you do not fully qualify the filename, the location of the file defaults to the current
subvolume.
Repeat steps 1 and 2 if you have chosen a configuration requiring more than one
authorization database.
Define the MPS Processes
You now need to define the MPS processes and their operational parameters. You can
use either of two template files for this purpose:
•
Use MPSCONF to establish a Pathway environment and define the MPS processes
as Pathway servers.
•
Use MPSCONFT to define an MPS process in the TACL environment.