Release Notes › Policy Server Release Notes › Known Issues › Unsupported Features › Upgraded Administrative UI Fails to Authorize Administrators in a New External Store

Upgraded Administrative UI Fails to Authorize Administrators in a New External Store

If you use the Administrative Authentication wizard to change the external administrator user store after upgrading the Administrative UI, restart the application server. If you do not restart the application server, the Administrative UI fails to authorize administrators.

Policy Server Performance with a Sun Java System Directory Server EE Policy Store

Symptom:

The Policy Server takes an exceedingly long time to start when version 6.0 of Sun Java System Directory Server EE is functioning as the policy store.

Solution:

A known indexing issue with version 6.0 results in the performance problem. Regenerate the existing policy store indexes.

Note: Version 6.3.1 of Sun Java Systems Directory Server EE contains fixes that affect the behavior of indexes. These fixes prevent the problem.

Important! The suffix DN is unavailable when you re–index the policy store.

To re–index the policy store

1. Log into the directory server host.
2. Navigate to the directory_server_install\bin and run the following command:

   dsadm reindex -b -t xpsNumber -t xpsValue -t xpsSortKey -t xpsCategory -t xpsParameter -t xpsIndexedObject
   -t xpsTombstone instance_path policysvr4
   

   directory_server_install

   Specifies the Sun Java System Directory Server EE installation path.

   instance_path

   Specifies the path to the directory server instance functioning as the policy store.

   Note: For more information about dsadm command, see your vendor–specific documentation.

3. Restart the directory server instance.

Sun Java System Directory Server EE Logs Warn that the Search is Not Indexed

Symptom:

I have configured version 6.3.1 of Sun Java System Directory Server EE as a policy store. The directory logs contain warnings stating that the search is not indexed.

Solution:

This is expected behavior and SiteMinder performance is not affected. Restart the directory server instance to stop the warnings.