If you have the qpm-server installed and you run Check Client for Policy Readiness from the mangement console and it tells you the policy server port is unavailable, check the port to see if another program is using that port.
When you navigate to the Policy tab, the browser checks for an available JRE (Java runtime Environment). If the browser detects that a JRE is not installed, it prompts you to install one. You must install the Sun JRE, which can take several minutes, before the applet initializes. After you have successfully installed Java, click Close.
|
Note: You must have the Sun JRE 1.6 or greater browser plugin installed on a supported platform to use the policy editor. |
If the Sun JRE 1.6 browser plugin fails to install, one possible resolution is to uninstall your browser and reinstall it, then install the JRE 1.6 browser plugin.
|
Note: To manage a policy file, you must log in either as the supervisor or an Active Directory account with rights to edit the policy file; that is, an account in the Manage Sudo Policy or Manage PM Policy role. |
Managing large policy files may affect the policy editor performance and you may need to give Java more memory.
To increase the Java applet memory limit
|
Note: See Java Control Panel for details about opening the Java Control Panel on Windows, Unix/Linux, or Mac OS X. |
|
Note: On Mac OS X
|
You can set it to anything between 64m and 512m.
The Policy Change Report reports newlines as a change in policy. All policy files have newlines at the end by default. If you open a policy in the GUI editor without newlines, it adds a newline to the end of each policy file. The Policy Change Report then reports this action as a change to the policy.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy