How to Re-Register the Symantec SiteMinder Administrative User Interface (UI)

Article By: Tiffany Kongpachith

For Using Either Fully Qualified Domain Name (FQDN) or IP Address on UNIX/Linux

The first time a user logs in to the Administrative UI with the default super user account (Symantec SiteMinder) and password; the Admin UI is registered with the Policy Server. Based on the client’s requirements, registering the Admin UI could be established through IP address or Fully Qualified Domain Name (FQDN). If the user registers from either method from the web browser, this document will provide the procedures to re-register the Admin UI from one method to the other.

Prerequisites

  • Assumption that the SiteMinder Policy Server has been fully installed and configured.
  • Assumption that the SiteMinder Administrative User Interface has been fully installed and configured.
  • Assumptions the SiteMinder Super User Account has been created for login credentials.
  • Assumption that the SiteMinder Admin UI has already been registered to the Policy Server and is ready for re-registering.
  • The user knows based on their implementation where the Administrative User Interface install directory is located.

Re-Register the Administrative User Interface (UI)

This section explains the various approaches to re-register the Administrative UI with Policy Server.

For instance if the customer originally registered the SiteMinder Admin UI with the IP address, the steps below provide how to re-register the Admin UI to be accessed via Fully Qualified Domain Name (FQDN).

A. With Policy Server Shut Down Method:

We recommend you follow this method to re-register Administrative UI.

Follow these steps:

1. Stop the Administrative UI service. (./jboss-cli.sh -c –command=:shutdown)

2. Stop the Policy Server. (./stop-all)

3. From the Administrative UI installation directory, navigate to /standalone directory.

4. Delete the folders: /data, /log, and /tmp.

5.Run the XPSRegClient command on the Policy Server machine.

XPSRegClient siteminder:<password> -adminui-setup

6. Start the Policy Server. (./start-all)

7. Start the Administrative UI service. (./standalone.sh)

8. Access the Administrative UI web page to complete the registration.
– The users can now access the Admin UI URL via Fully Qualified Domain Name (FQDN) or vice versa.

For example: https://siteminderadminui.com:[port]/iam/siteminder/adminui

B. Without Policy Server Shut Down:

1. Stop the Administrative service. (./jboss-cli.sh -c –command=:shutdown)

2. From the Administrative UI installation directory, navigate to /standalone directory.

3. Delete the folders – /data, /log, and /tmp.

 

 

 

 

4.Using the XPSExplorer utility, remove the trusted host that is created by XPSRegClient.
For information about deleting the trusted host, see the section XPSExplorer-delete Trustedhost below.

5. Using the XPSSecurity utility, remove the Administrative UI directory.
For information about deleting the Administrative UI directory, see the section XPSSecurity-delete Administrative UI Directory below.

6. Run the XPSRegClient command on the Policy Server machine.
XPSRegClient siteminder:<password> -adminui-setup

7. Start the Administrative UI service. (./standalone.sh)

8. Access the Administrative UI web page to complete the registration.
– The users can now access the Admin UI URL via Fully Qualified Domain Name (FQDN) or vice versa.

For example: https://siteminderadminui.com:[port]/iam/siteminder/adminui

Looking for additional help with re-registering the Symantec SiteMinder admin UI? ISX Consulting is an elite IAM security firm that offers boundless expertise in a range of cybersecurity and business process services, including Symantec SiteMinder. Take your interoperability to the next level, and contact an ISX consultant today.

ISXHow to Re-Register the Symantec SiteMinder Administrative User Interface (UI)

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *