Changing to an external Remedy Single Sign-On instance after installation
If you are using the embedded version of Remedy Single Sign-On (Remedy SSO) authentication and you want to switch to an external Remedy SSO instance, all BMC Atrium Orchestrator (BAO) components that point to embedded Remedy SSO must be reconfigured to point to the external Remedy SSO instance.
- Complete these instructions only if you are changing to an external Remedy SSO.
- If you make this change, the instructions in Configuring a fail-safe enterprise service bus after installation or Configuring a fail-safe enterprise service bus after upgrade do not apply.
The following BAO components must be reconfigured:
- OCP (if installed)
- HA-CDP (if installed)
- AP (if installed)
In these instructions, AO_HOME represents the component installation directory.
To configure components for an external Remedy SSO, complete the following steps for each component.
- Stop the component service (see Starting and stopping product components and services).
- Navigate to the AO_HOME/config directory.
Edit the authentication.xml file.
The file will look similar to the following example:
Change the authentication service-type and URL settings to those for the external Remedy SSO as follows:
- Navigate to the AO_HOME/tomcat/conf directory.
- Edit the context.xml file.
Locate the following lines and, if they exist, comment them out, and save your changes.
Note that the port numbers and IP address values will be different in your file.
- Restart the BAO component service.
Create the default user, role, and realm
Perform these steps after you have changed your authentication system to external Remedy SSO.
After installing Remedy SSO, you must complete the following tasks before installing BMC Atrium Orchestrator Platform components:
- Create a realm named BAOLocal (see Working with realms).
- Create a user called aoadmin (see Creating and managing local users and roles in Remedy Single Sign-On). Use the default password (see Installing the repository for the default password, which is listed after the installation instructions).
- Create a role called AoAdmin (see Creating and managing local users and roles in Remedy Single Sign-On).
- Assign the aoadmin user to the AoAdmin role (see Creating and managing local users and roles in Remedy Single Sign-On).