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

Java Applet Failures

To use specific features such as the SSH to Host feature or the Privilege Manager Policy editor, you must install the Sun JRE (Java Runtime Environment) 1.6 browser plugin.

Note: ava applets may be blocked from running in Firefox 18 with older Java versions (prior to 1.7). If you are not be able to view policies or SSH to hosts, you can resolve the issue by uninstalling the older version of Java and installing the latest version. Because of the frequent updating of Firefox and Java Plugin, the editor applet and/or mindterm SSH applet might produce security issues when loading applets. Make sure you are using the latest versions of both Firefox and the Java Plugin on the client you use to access the console.

If you have attempted to use SSH to Host or the policy editor, but they failed to run, One Identity recommends the following troubleshooting steps:


If you are using an Internet Explorer browser, you may need to reset your Download options.

To modify the Download Internet options

  1. From your Internet Explorer browser, navigate to Tools | Internet Options and click the Security tab.
  2. In the Security Settings dialog, click the Custom level... button, scroll down to Downloads, and ensure that the Automatic prompting for file downloads and File download settings are set to Enable.
  3. Try SSH'ing to the host again. If you still fail, proceed to step II.

Confirm that you have a valid Sun JRE (Java Runtime Environment) 1.6 or greater browser plugin installed.

To verify your version of Java

  1. Visit .
  2. Verify that you have the Sun JRE (Java Runtime Environment) 1.6 or higher browser plugin installed.
  3. Try SSH'ing to the host again. If you still fail, proceed to step III.

Validate that the correct applet .jar files were downloaded to the client.

Note: SSH to Host requires mindterm.jar and the policy editor requires editor.jar.

To validate the Java applet files

  1. Start the Java Control Panel.

    Note: (See Java Control Panel for details about opening the Java Control Panel on Windows, Unix/Linux, or Mac OS X.)

  2. On the General tab of the Java Control Panel, click the View button.

    Note: On Mac OS X, in the General tab, select the current Java version and click the Options button.

  3. Verify that the mindterm.jar file (used for SSH to Host) or the editor.jar file (used for the policy editor) are listed in the Java Cache Viewer dialog.

    Note: If these .jar files are there, yet the SSH to Host function or the policy editor failed to run, try uninstalling your browser and your Java browser plugin and reinstalling it.

  4. Try SSH'ing to the host again. If you still fail, contact Technical Support at

Problem: When running the mangement console by means of a browser on a VMware ThinApp, SSH to Host fails initially. An exception displays that says, "Error: Click for details". The details indicate the application failed to run because a MindTerm class was not found. The VMware ThinApp is not accepting the Java certificate. This only occurs on the initial launch of the MindTerm application.

Work Around: Run the mangement console with a resident browser. When you SSH to Host, a Warning-Security message displays that says, "The application digital signature cannot be verified. Do you want to run the application?" Select the "Always trust content from the publisher" option and click Run. Once the Java certificate is accepted by a resident browser, you can SSH to Host with any browser.

Java Control Panel

To open the Java Control Panel

  • From the Start menu, open the Windows Control Panel, view by icons, and click the Java link to open the Java Control Panel.

    Note: You may have to switch to "classic view" to display all icons. On 64-bit operating systems the Java icon is in a separate folder called "View x86 Control panel icons".

  • Start the Java Control Panel from the command line. You can find it in your Java installation directory. A possible location would look like this:
Mac OS X
  • On Mac OS X 10.5, navigate to Applications | Utilities | Java and open Java Preferences.
  • On Mac OS X 10.6 (and greater), from the "Go" menu, choose Utilities and double-click Java Preferences.

License Info in Report is not Accurate

The pmloadcheck daemon runs on each configured policy server to verify its status. It controls load balancing and failover for connections made from the host to the configured policy servers, and, on secondary servers, it sends license data to the primary server.

The Product License Usage report is only accurate up to the last synchronization interval which by default runs every 60 minutes.

Note: The Product License Usage report does not include trial license information.

Out of Memory Error

If you see java.lang.OutOfMemoryError in the logs then may need to adjust your JVM memory allocation. (See JVM Memory Tuning Suggestions for details.)

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating