Safeguard Authentication Services 4.1.5 - Management Console for Unix Administration Guide

Default Logon Domain

The mangement console uses the default log-on domain to authenticate the user name you use when logging onto the console.

To set the default log-on domain

1. Log into the mangement console with the supervisor account or an Active Directory account with rights to change System Settings; that is, an account in the Console Administration role.
2. From the top-level Settings menu, navigate to System settings | Active Directory and click the Advanced Settings button.
3. On the Active Directory Credentials dialog, enter a user name and password to authenticate to Active Directory.

   The Active Directory Forest Configuration dialog displays.

4. Next to Default logon Domain (at the bottom of the dialog), choose the default domain to use when logging onto the console.

   This allows you to log onto the mangement console using a simple name instead of "user@domain".

5. Click Verify configuration. (Note: You must test before you can save the change.).
6. Click OK to return to System Settings.

Privilege Manager System Settings

You can configure the mangement console to communicate with one or more Privilege Manager policy groups which allows you to centrally manage security policy, remotely configure the Privilege Manager hosts, and view keystroke logs generated by the policy. The Privilege Manager settings in System Settings allows you to activate previously configured service accounts on policy servers. This enables you to view and edit the policy, view keystroke logs, and run policy reports.

Use the Privilege Manager settings to configure the service account and activate the policy groups that you want to use for checking policy and keystroke logging.

Before you can use the Privilege Manager features, you must install and configure a Privilege Manager primary policy server. (See Install the Privilege Manager Packages for details.)

Configure a Service Account

Configuring a service account activates the policy group and allows the console to access both pmpolicy or sudoers policy files, view events and keystroke logs for a policy group.

To configure service account

1. Log in as supervisor or an Active Directory account with rights to change System Settings; that is, an account in the Console Administration role.

2. From the top-level Settings menu, navigate to System settings | Privilege Manager.

3. Click Configure service account next to the primary policy server listed.

   Note: If your policy group is not listed, make sure you have added and profiled the host where Privilege Manager software is installed as the primary policy server to the mangement console; then re-profile the host.

4. On the Configure Service Account dialog, enter credentials to log onto the primary policy server and click OK.

   Note: This task requires elevated credentials.

5. Verify that the Active box is checked and click OK to save System Settings.

When you configure the service account, the mangement console,

1. Creates "questusr", (the user service account), if it does not already exist, and a corresponding "questgrp" group on the host.

   Note: The questusr account is a user service account used by Management Console for Unix to manage Privilege Manager policy and search event logs. It is a non-privileged account (that is, it does not require root-level permissions) used by the console to gather information about existing policy servers and commit policy changes. questgrp is the primary group (gid) for questusr.

2. Adds questusr to the pmpolicy and pmlog Privilege Manager configuration groups, and as an implicit member of questgrp.

   Note: questusr, pmpolicy, and pmclient are all non-privileged service accounts (that is, they do not require root-level permissions). The pmpolicy and pmclient users are used to sync the security policy on policy servers and on Sudo Plugin hosts (offline policy cache), respectively. The pmlog and pmpolicy groups are used to control access to log files and the security policy, respectively.

3. Adds the policy group SSH key to questusr's authorized_keys, /var/opt/quest/home/questusr/.ssh/authorized_keys.
4. Verifies the user service account can login to the host.

   Note: If you receive an error message saying you could not log in with the user service account, please refer to Service Account Login Fails to troubleshooting this issue.

If questusr is inadvertently deleted from the console,

1. Re-profile the host.
2. Unconfigure the service account. (See Unconfigure a Service Account for details.)
3. Reconfigure the service account.

Unconfigure a Service Account

Unconfiguring a service account deactivates the policy group in the mangement console and disables console access to the policy file and keystroke logs on the primary policy server.

To unconfigure service account

1. Log in as supervisor or an Active Directory account with rights to change System Settings; that is, an account in the Console Administration role.
2. From the top-level Settings menu, navigate to System settings | Privilege Manager.
3. Click Unconfigure service account next to the primary policy server listed.
4. On the Unconfigure Service Account dialog, enter credentials to log onto the primary policy server and click OK.

   Note: This task requires elevated credentials.

5. Verify that the Active box is not checked.