Frequently Asked Questions for P-Synch Administrators
How do I reset the superuser application ID's password?
In the event that the P-Synch® administrator forgets his own application password into P-Synch, P-Synch comes with the ADM_SET utility that allows a user with an administrative console login on the P-Synch server to reset the P-Synch application administrator password. This program can also be used to unlock/enable a superuser ID. ADM_SET is only accessible from an administrative command prompt on the P-Synch server.
Where does P-Synch store Q&A data?
P-Synch normally stores Q-A (Question-and-Answer) data, used to authenticate users who forget their passwords, in its internal identity cache. The questions and answers are encrypted using 128-bit AES using a secret key. Alternatively, P-Synch can be tied to an external repository (e.g., LDAP, AD, Oracle, etc.) where it reads and writes Q-A (Question-and-Answer) data and login ID profiles.
How do I write reports that directly query the P-Synch database?
P-Synch stores data using an embedded database engine, which acts both as an identity cache (managing a rolling snapshot of information about users drawn from target systems) and as a place to store configuration information and persistent user data, such as password history.The identity cache is local to the P-Synch server, which makes the user interface much more responsive. It is not authoritative for user profile data, as data is refreshed from target systems regularly and automatically (typically every night).
The following data is stored in P-Synch:
- User profiles:
- User ID, name (plaintext)
- Login IDs attaching users to managed systems (plaintext)
- Password history (Hashed, salted old passwords)
- Authentication profile (Optional. If stored, encrypted using 128-bit AES and a server-designated 128-bit key.)
- System configuration:
- Target system information
- Target system login credentials (encrypted: 128-bit AES and a server-designated 128-bit key)
- Password policy rules
- List of events that should be intercepted and trigger outbound integration with systems such as BMC/Remedy ARS
- Various other configuration data
- System event logs -- capturing historical events, including:
- Requesting user.
- Target/recipient user.
- Target system involved, if any.
- Operation.
- Time/date.
- Result code and message.
These logs are typically retained indefinitely, for reporting purposes.
P-Synch comes with various "canned" reports that can be generated through the web interface. To access these reports:
- Log in as an admin user who has the right to view the server monitor.
- Click Server Monitor → Run Reports to see the P-Synch Run Reports page.
- Click on the type of report you want to generate.
Additionally, if custom reports need to be created, then the database files can be copied to another location. This will allow another tool to read the database and allow you to generate custom reports.