Configuring the access manager
The access manager listens for incoming connections from the SafeLinx Administrator so that you can configure the SafeLinx Server. After you configure the access manager a new wizard opens so that you can add a SafeLinx Server.
On AIX or Linux, you do not use separate wizards to configure database storage and configure the access manager. Instead, you configure the access manager through the same initial configuration wizard that guides you through the process of setting up databases. After you complete the database configuration steps in the wizard, you can configure the access manager as described in the procedure that follows. For information about using the configuration wizard to set up database connections, see Completing the initial DB2 database configuration on AIX or Linux or Configuring Oracle.
After you complete the database configuration, either through the Configure the SafeLinx Server Access Manager wizard on AIX or Linux, or the Database Configuration Wizard on Windows, you begin the access manager configuration.
In the Base distinguished name (DN) field, accept the default DN
(c=local), or specify a different DN if you want the SafeLinx Server to store
configuration data in a specific branch of the organizational hierarchy.
The base distinguished name is used to create a directory structure that provides a unique key for locating SafeLinx Server resources. Using standard X.500 notation, specify a base distinguished name that designates the root node or suffix of the primary organizational unit for this SafeLinx Server. This field is case-sensitive.
For example, to specify a root node, you might type something like o=hcl,c=us. To specify an entry point that is contained in subordinate node of the directory tree, you might type ou=la,ou=ca,o=hcl,c=us.
- In the section, Store configuration data using, click The same method as chosen for session data storage.
If you want to allow admins to log in remotely with the default admin ID, admin, select
Allow super user administrator IDs to log in remotely from SafeLinx
By default the super user admins are allowed to log in remotely from the SafeLinx Administrator.Note: AIX and Linux, users who log in using the operating system root ID have the same access to resources as the default administrator (admin). This access includes remote access.
If you want remote SafeLinx Administrator sessions to occur over secure TLS connections only, select
Force remote SafeLinx Administrator connections to use SSL.
To ensure privacy, use encrypted connections between remote SafeLinx Administrator installations and the SafeLinx Server.
Specify the access manager and secure access manager log file locations and log levels.
The log levels that you specify apply to the log files wgmgrd.log and wgmgrsd.log. By default, the access manager logs are disabled. If you retain the default, you can edit the access manager properties later to enable logging. Enable logging when you want to troubleshoot access manager problems.
Click Next, and then, click Finish.
You have now supplied all of the information to configure the access manager.
- After the Configure the SafeLinx Server Access Manager wizard closes, you are prompted to modify the admin superuser account. Click Yes, if you want to change the default password. Otherwise, click No to continue on to the SafeLinx Server configuration.