Installation Guides › Policy Server Installation Guide › Troubleshooting › Administrative UI Troubleshooting › HTTP Status: 404 Error Appears

HTTP Status: 404 Error Appears

Problem:

I receive an HTTP Status: 404 error message when I try to log in to the Administrative UI.

Consider the following solutions:

Solution 1:

If you are trying to register the Administrative UI with the Policy Server, some or all of the administrator user store credentials you entered when installing the Administrative UI are incorrect.

1. Verify the following information:
   • Administrator credentials—The directory manager credentials (LDAP) or the database administrator credentials (ODBC) used to connect to the administrator user store may be incorrect.
   • Administrative UI Super User—The default Super User's user DN (LDAP) or account name (ODBC) may be incorrect.
2. Re-install the Administrative UI with the correct administrator user store credentials.

   Note: If you have not exceeded the registration timeout value, you do not have to run XPSRegClient again to create a client name and passphrase. The default timeout value is four (4) hours.

Solution 2:

The object store Administrative password may have changed. If the password has changed, update the application server's datasource definitions with the new datasource password.

To update the datasource password for WebLogic or WebSphere, use the vendor-specific administrative tool.

Note: See you vendor-specific documentation for more information on updating datasource passwords.

To update the datasource password for JBoss

1. Obtain the new password.
2. Navigate to one of the following in a console window:
   • (Windows) admin _ui_home\CA\IAM Suite\siteminderWAM\tools \PasswordTool
   • admin_ui_home

     Specifies the Administrative UI installation path.

   • (UNIX) /opt/CA/IAM_SUITE/siteminderWAM/tools/PasswordTool
3. Run the following command:
   • (Windows) pwdtools -JSAFE -p password
   • (UNIX) ./pwdtools.sh -JSAFE -p password
   • password

     Specifies the Administrative password for the object store.

   The password utility encrypts the password.

4. Copy the encrypted password.
5. Navigate to jboss_home\server\server_name\conf and open the login-config.xml file.
   • jboss_home

     Specifies the JBoss installation path.

   • server_name

     Specifies the name of the JBoss server.

6. Locate the following policy application sections in the login-config.xml file:
   • <application-policy name="objectstore-login">
   • <application-policy name="reportsnapshot-login">
   • <application-policy name="imtaskpersistencedb-login">
   • <application-policy name="imauditdb-login">

   Each of these sections includes a <module-option name="password"> parameter.

7. Replace the existing value of each instance of the module-option name parameter with the new encrypted value.
8. Save the file.
9. Restart JBoss.