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

Reports Are Slow

The console may appear to "stick" in the data collection phase while generating reports.

To troubleshoot this issue, consider these possible reasons:

  • You are reporting on a large dataset
  • You have a slow connection with Active Directory
  • Your network connection is slow
  • The JVM memory size is too small (See JVM Memory Tuning Suggestions for details.)

Reset the Supervisor Password

The supervisor is the only account that has rights to change the supervisor account password in System Settings.

You entered the password for the supervisor account when you initially configured Management Console for Unix. (See Set Supervisor Password Dialog for details.)

The easiest way to change the supervisor password, is to log into the console as the supervisor, navigate to System Settings | General | Change Password and modify it there. If you have forgotten the current supervisor account, you can reset the supervisor password by making changes to the configuration file. However, you must have administrator rights on the computer to access the file.

To reset the supervisor password

  1. Locate the custom.cfg file.

    (See Setting Custom Configuration Settings for more information about customizing configuration settings for the mangement console.)

  2. Add the following line to the end of the file:

    where new_password is the new password.

  3. Save the custom.cfg file.
  4. Restart the Management Console for Unix service.
  5. Log onto the mangement console as supervisor and provide the new password.
  6. Remove the line added in Step 2 from the custom.cfg file and save the configuration file.

Note: If you leave the -Dforce.supervisor.password.reset parameter in the custom.cfg file, the mangement console will reset the specified password each time you start the service.

Running on a Windows 2008 R2 Domain Controller

When running Management Console for Unix on a Windows 2008 R2 Domain Controller, you must change your User Account Control Settings.

To change your User Account Control Settings

  1. From the Start menu, navigate to Control Panel | User Account | User Accounts | Change User Account Control settings.

  2. On the User Account Control Settings dialog, adjust the notification level to Never notify and click OK.

Service Account Login Fails

There could be several reasons why you might receive an error message saying you could not log in with the user service account:

  • Account does not exist
  • Account has been disabled
  • Account has invalid gid or login shell
  • SSH server is not running
  • SSH keys are not configured properly
  • SSH server is not configured to allow login by means of SSH key
  • SElinux may be disallowing access to SSH server files needed for SSH key authentication

To troubleshoot your login failure,

  • Check your SSH server configuration to verify that public key authentication is enabled. (Refer to your SSH server configuration instructions for details.)
  • Test SSH key authentication with another user.
  • Reconfigure or disable SELinux.

Note: Configuring a service account on a host with Security-Enhanced Linux (SELinux) enabled might fail due to the enhanced security-related restrictions on the system. Please contact Technical Support at for instructions on how to either reconfigure or disable SELinux.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating