Chat now with support
Chat with Support

Safeguard Authentication Services 4.1.5 - Management Console for Unix Administration Guide

One Identity Privileged Access Suite for Unix Introducing One Identity Management Console for Unix Installing Management Console for Unix Preparing Unix Hosts Working with Host Systems Managing Local Groups Managing Local Users Active Directory Integration Authentication Services Integration Privilege Manager Integration Reporting Setting Preferences Security Troubleshooting Tips
Auto Profile Issues Active Directory Issues Auditing and Compliance Cannot Create a Service Connection Point Check Authentication Services Agent Status Commands Not Available CSV or PDF Reports Do Not Open Database Port Number Is Already in Use Elevation Is Not Working Hosts Do Not Display Import File Lists Fakepath Information Does Not Display in the Console Java Applet Failures License Info in Report is not Accurate Out of Memory Error Post Install Configuration Fails on Unix or Mac Privilege Manager Feature Issues Profile Task Never Completes questusr Account was Deleted Readiness Check Failed Recovering From a Failed Upgrade Reports Are Slow Reset the Supervisor Password Running on a Windows 2008 R2 Domain Controller Service Account Login Fails Setting Custom Configuration Settings Single Sign-on (SSO) Issues JVM Memory Tuning Suggestions Start/Stop/Restart Management Console for Unix Service Tool Bar Buttons Are Not Enabled UID or GID Conflicts
System Maintenance Command Line Utilities Web Services Database Maintenance

Rename Host

Note: You can only rename a host that has not been profiled.

To rename host(s)

  1. Select a host on the All Hosts view and click Rename Host from the Host panel of the tool bar.
  2. In the Rename Host dialog, enter the FQDN, IP address or short name to use to connect to that host.
  3. Optionally, you can deselect the Profile host now option.
  4. Click OK.

If the Profile host now option option was selected, the mangement console starts the Profile Host procedure. (See Profile Host(s) for details.)

Profile Host(s)

Profiling imports information about the host, including local users and groups, into the mangement console. It is a read-only operation and no changes are made to the host during the profiling operation. Profiling does not require elevated privileges.

To profile host(s)

  1. Select one or more hosts on the All Hosts view and click Profile from the Prepare panel of the tool bar, or open the Profile menu and choose Profile.
  2. In the Profile Host dialog, enter user credentials to access the host(s).

    If you selected multiple hosts, you are asked if you want to use the same credentials for all the hosts (default) or enter different credentials for each host.

  3. If you selected multiple hosts and the Use the same credentials for all selected hosts option, enter the following information:
    1. Enter the user name and password to log onto the selected host(s).
    2. Optionally enter the SSH port to use. It uses port 22 by default.
    3. To save the credentials entered for the host, select the Save my credentials on the server option.

      Once saved, the mangement console uses these credentials to access the host during this and subsequent sessions.

    Note: If you do not save a password to the server, the user name and password fields will be blank the first time the mangement console needs credentials to complete a task on the host during a log on session. Once entered, the mangement console caches the user name and password and reuses these credentials during the current session, and pre-populates the user name and password fields in subsequent tasks during the current log on session.

    If you choose to save a host's credentials to the server, the mangement console encrypts the credentials and saves them in the database. Saved user names and passwords persist across log on sessions, and when needed, the mangement console pre-populates the user name and password fields the first and subsequent times it needs them to perform a task. (See Caching Unix Host Credentials for more information.)

  4. If you selected multiple hosts and the Enter different credentials for each selected host option, a grid displays allowing you to enter different credentials and specify different settings for each host.
    1. To enter different credentials, place your cursor in the Username and Password columns to the right of the Host column and enter the credentials to use.
    2. To change the SSH port for a host, place your cursor in the SSH Port column and enter the new SSH port number.
    3. To save the credentials entered for a host, select the check box in the Save column.
  5. If you want the mangement console to prompt you to review and accept new SSH keys for the selected hosts (that do not have previously cached SSH keys), clear the Automatically accept SSH keys option before you click OK.

    Note: When profiling one or more hosts, you must accept at least one key before continuing. The mangement console only profiles hosts with accepted keys.

    By default the Automatically accept SSH keys option is checked. This enables the mangement console to automatically accept SSH key for all selected hosts that do not have a previously cached key. When it accepts the key, the console adds it to the accepted-keys cache on the Management Console for Unix server. If you clear the Automatically accept SSH keys option, when the mangement console encounters a modified key, it opens the Validate Host SSH Keys dialog, allowing you to manually accept keys that are encountered. Once you have manually verified the fingerprint, the console adds the SSH host key(s) to the accepted-keys cache.

    Note: Once you profile a host, all future tasks that involve an SSH connection will verify the SSH host key against the accepted-keys cache. When profiling, if the console encounters a modified key, the profile task prompts you to accept new/changed key(s). When performing any other SSH action, other than profile, if the console encounters a different SSH key, the task will fail. To update the accepted-keys cache for the host, you can either profile/reprofile the host, accept the new key, and try the task again. Or, you can import a new SSH host key from the host's properties or from the All Hosts view.

    See Import SSH Host Key or Managing SSH Host Keys for more information.

A progress bar displays in the Task Progress pane. The final status of the task displays, including any failures or advisories encountered.

Profile Hosts Automatically

To keep the Management Console for Unix database up to date with accurate information about users, groups, and One Identity products, you can configure the mangement console to profile hosts automatically.

best practice: As a best practice, configure newly added hosts for auto-profiling before you perform any other actions so that the mangement console dynamically updates user and group information. (See UID or GID Conflicts.)

Configuring a host for auto-profiling sets up a cron job on the client that runs every five minutes. If it detects changes on the host, it triggers a profile operation.

The cron job detects changes to the following:

  • local users, groups, or shells
  • installed Authentication Services or Privilege Manager software
  • Authentication Services access control lists
  • Authentication Services mapped user information
  • Privilege Manager configuration
  • Authentication Services configuration
  • Privilege Manager licenses

The cron job also sends a heartbeat every day. This updates the Last profiled date displayed on the host properties. If the Last profiled date is more than 24 hours old, the host icon changes to to indicate no heartbeat.

To configure automatic profiling

  1. Select one or more hosts on the All Hosts view, open the Profile menu from the Prepare panel of the tool bar, and choose Profile Automatically...

    Note: The Profile Automatically option is only available for multiple hosts if all hosts are in the same ‘Auto-profile’ state; that is, they all have ‘Auto-profile’ turned on, or they all have ‘Auto-profile’ turned off.

  2. In the Profile Automatically dialog, select the Profile the host automatically option.
  3. Choose the user account you want to use for profiling, either:
    1. Create a user service account on the host

      When you choose to create the user service account on the host, if it does not already exist, the mangement console, does the following:

      1. Creates "questusr", the user service account, and a corresponding "questgrp" group on the host that the mangement console uses for automatic profiling.
      2. Adds questusr as an implicit member of questgrp.

      -OR-

    2. Use an existing user account (user must exist on all selected hosts)

      (Click Select to browse for a user.)

  4. Click OK on the Profile Automatically dialog.

    Whether you choose to create the user service account or use an existing user account, the mangement console,

    • Adds the user account (the "questusr" or your existing user account) to the cron.allow file, if necessary. For example, the console takes no action if the cron.allow file does not already exist, but there is a cron.deny file:

      When the user is added to the cron.allow file

      cron.allow cron.deny Console’s action Resultant User Access
      NO NO Creates cron.allow and adds root and questusr to it Both root and questusr have access.
      NO YES No action All users have access except those in cron.deny; questusr has access unless explicitly denied.
      YES NO Adds questusr to cron.allow Users in cron.allow have access.
      YES YES Adds questusr to cron.allow Users in cron.allow have access unless in cron.deny.
    • Adds a cron job to the questusr account to execute chgfmon utility that monitors changes. chgfmon logs change events to syslog.
    • Creates a second cron job to monitor the host connectivity to the server.
    • Adds the auto-profile SSH key to questusr's authorized_keys, /var/opt/quest/home/questusr/.ssh/authorized_keys.
    • 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.

    The questusr account is a non-privileged account that does not require root-level permissions. This account is used by the console to gather information about existing user and groups in a read-only fashion, however, the mangement console does not use questusr account to make changes to any configuration files.

    If questusr is inadvertently deleted from the console, the console turns ‘Auto-profiling’ off.

    To recreate the "questusr" account,

    1. Re-profile the host.
    2. Reconfigure the host for automatic profiling.
  5. On the Log on to Host dialog, enter the user credentials to access the selected host(s) and click OK.

    Note: This task requires elevated credentials.

    If you select multiple hosts, you are asked if you want to use the same credentials for all the hosts (default) or enter different credentials for each host.

    1. If you selected multiple hosts and the Use the same credentials for all selected hosts option, enter your credentials to log on to access the selected host(s) and click OK.
    2. selected host option, it displays a grid which allows you to enter different credentials for each host listed. Place your cursor in a cell in the grid to activate it and enter the data.

To disable automatic profiling

  1. Select one or more hosts on the All Hosts view and choose Profile Automatically...
  2. Clear the Profile the host automatically option and click OK.
  3. On the Log on to Host dialog, enter the user credentials to access the selected host(s) and click OK.

When you disable auto-profiling for a host, the mangement console,

  1. leaves the "questusr" and the corresponding "questgrp" accounts on the host, if they were previously created.
  2. leaves questusr as an implicit member of questgrp, if it exists.
  3. removes the user account (the "questusr" or your existing user account) from the cron.allow file.
  4. removes the auto-profile SSH key from that user's authorized_keys file.

View the Auto-Profile Status

You can view the automatic profile failures or warnings on the Host Notification tab.

To view the auto-profile status

  1. From the Host Notifications tab, select the Auto-Profile Status tab.

    Note: If the Host Notifications tab is not currently available on the mangement console, open the Open views menu from the Tab bar (represented by a "tab" icon ) and choose the Host Notifications option.

    The Auto-Profile Status tab displays the following alert for hosts where there has been a failure to auto-profile:

    - Auto-profile failed

  2. To re-profile or re-set the auto-profile settings for one or more hosts, select the host(s) on the Auto-Profile Status tab, open the Profile menu from the tool bar, and choose either Profile or Profile Automatically...

    Note: The Profile Automatically option is only available for multiple hosts if all hosts are in the same ‘Auto-profile’ state; that is, they all have ‘Auto-profile’ turned on, or they all have ‘Auto-profile’ turned off.

Related Documents