GSX ID Manager - Evaluation version
- 1) Launch the self-extracting program attached above and follow the instructions of the InstallShield installation wizard
2) Sign databases
3) Update database ACLs
4) Open the Local ID Manager database to enter the configuration Wizard
5) Copy Certifiers to be used during your tests into the Archive database configuration document
6) Activate the agent, in the Central ID Manager database. It is used to send encrypted email with ID's passwords. Note: this feature may not available in the evaluation version.
That's it. Now, you can create some requests from the Local ID Manager database.
7) Create a new user request, it has to start with letter "A" in evaluation version. When sent, the request should be visible in the Central ID Manager database. If not, please check your Mail-in database documents.
8) Approve the request in the Central ID Manager database
9) From the server's Windows' Start menu, launch Start - Program - GSX Products - GSX ID Manager (if you did not install in the default directory, Windows will prompt you to search for the new file, press OK)
10) In case the status of the request did not change, it's most likely due to an incomplete configuration, check that:
a) The certificates in the ID Manager Archive database - Administration - Certificates are enabled (press the button on the left side)
b) That all system forms are completed, especially that they contain the valid Mail-in database names
The .dbg files automatically created in the debug directory may help you in case of problem. If not, don't hesitate to contact us: firstname.lastname@example.org.
- Notes Versions: Notes R5.0.4 or later
- Evaluation version type
The self extracting file below contains evaluation databases with hidden design. Some security features have been removed to allow you to access secured parts of the databases.
You are entitled to use any evaluation software only over a period of 30 days. The trial version allows only requests starting with the letter "A".
During the evaluation, GSX recommends to install all 3 databases and the API program on the same Domino server.
The GSX ID Manager package contains:
- the Local ID Manager database (DB used to create and send requests)
- the Central ID Manager database (Mail-in DB that gathers all requests)
- the Archive ID Manager database (Archive database containing ID's passwords, track of requests)
- the API program used to process requests Normal 0 21 false false false MicrosoftInternetExplorer4
The Local ID Manager database can be installed once or several times depending on your needs. For example, one DB can be installed per region or per office or per HR service responsible of managing users. The Central, Archive databases and the API must be placed on the same server. For the tests, GSX recommends to make it simple and install all 3 databases and the API program on the same server.
Make sure there was no add-in product such as Candle Intelliwatch previously installed on the machine where the API program has to be installed. Some software, including Intelliwatch, replace some of the standard Notes components (Dlls) and make them unusable to any other add-on program. In case such a product has been previously installed, you need to delete the previous Domino installation, delete all Domino Dlls and reinstall from scratch or use a clean installation. GSX Server Guard does not alter the original Domino configuration and is therefore compatible with GSX ID Manager.
Workflow for a new user ID:
1) A request is created in the Local database. When saved, it is sent out to the Central ID Manager database
2) The request is validated (by pressing the Approve button)
3) Periodically, the API program will run and process all pending requests. You can simulate this step - so that you don't have to wait - by launching the ID Manager program using the Windows menu.
4) The API program generates the ID and password. Both are saved in the Archive database(s). In addition, the ID is sent back to the Local ID Manager DB (by email) and the password is sent to the requester of the request (in an encrypted email), once the agent in the Central ID Manager database has run.
This is the way it works in the standard product. Changes can be done to adapt it to your Company's requirements.