OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-26
MPS Concepts and Components
•
The encryption method
•
Whether to log requests in an audit trail
•
The name of the audit-trail file
•
Whether to log bind requests (or only other types of requests)
•
Whether to write passwords to the audit-trail file
•
Master user information:
•
The master user APPL name
•
The master user APPL OSI address
•
The encryption method for the master password
•
The master password (encrypted)
•
The master user O/R name
•
Whether the master user may bind under its own APPL name
•
Whether the master user may register under its own APPL name
Multiple MPS processes can share a configuration database (and so represent the same
master user) to balance the validation workload. In such cases, any of the MPS
processes can read or write to the database. Therefore it is important that all processes
be informed of updates to the master user and MPS option information. The MPS uses a
CONTROL 27 (Wait for Disk File Write) system procedure call to detect changes in the
configuration database file.
If different master users are to be assigned to different mailboxes, then the set of MPS
processes representing the same master user share a configuration database, and the
MPS processes representing different master users have different configuration
databases.
The MPS modifies the configuration database:
•
When the first MPS is started up—that MPS process creates and loads the
configuration database.
•
When an MPS process is run in a special RECONFIGURE mode.
•
When an ADD, DELETE, or ALTER command applies to the APPL of the master
user. (Note that if you delete the master user, the MPS can still perform its other
validation functions.)
The configuration database and updates to it are protected by TMF.
Authorization Database
Each MPS process, even when processes share a configuration database, has its own
authorization database, containing information about the MS APPLs supported by that
MPS process. No two MPS processes can support the same APPL, and all APPLs
defined for the same MS group must be supported by the same MPS process.