Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Installing an authentication service before BAO 7.7.x, 7.8.x, and 7.9.00 with ASSO upgrades to 7.9.01 with RSSO

You can use one of the following BMC Remedy Single Sign-On (Remedy SSO or RSSO) authentication service options:

  • Embedded Remedy SSO: Use this option when you upgrade the BAO repository, CDP, and/or HA-CDP. Remedy SSO is installed with the BAO upgrade (you do not install it separately).
  • External Remedy SSO:  Install a supported version of Remedy SSO on a separate server before upgrading BAO Platform components.  See 7-9-01-Service-Pack-1 for the supported Remedy SSO version.

Notes

  • Install an external Remedy SSO only if you are not installing the embedded Remedy SSO with the BMC Atrium Orchestrator (BAO) Platform upgrade.
  • If you are installing an external Remedy SSO authentication service, install it first (prior to upgrading BAO Platform components).
  • This upgrade does not support migrating users and groups from Atrium Single Sign-On to Remedy Single Sign-On. You need to recreate your users, groups, and group assignments when Remedy SSO is installed in your environment (see Creating-and-managing-local-users-and-roles-in-Remedy-Single-Sign-On).
    • If you are upgrading with the embedded Remedy SSO service, after the upgrade, in Remedy SSO recreate your local users and groups (called roles in Remedy SSO) and assign users to the appropriate roles.
    • If you are upgrading with an external Remedy SSO service, before or after the upgrade, in Remedy SSO recreate your local users and groups (called roles in Remedy SSO) and assign users to the appropriate roles.
  • Remedy Single Sign-On versions 9.1.01.001 and 9.1.02.001 only support BMC Atrium Orchestrator high availability with an embedded database. Stand-alone Remedy SSO versions 9.1.01.001 and 9.1.02.001 installations do not support HA with embedded DB.

This topic includes the following information:

Embedded Remedy SSO

If you install the embedded Remedy SSO during the BAO Platform installation, a realm named BAOLocal is automatically created during the installation of the repository, CDP, and HA-CDP if it is installed.

External Remedy SSO

Complete the steps in this section to use an external Remedy SSO.
NoteInstall an external Remedy SSO only if you are not installing the embedded Remedy SSO with the BMC Atrium Orchestrator (BAO) Platform installation.

Install Remedy SSO

To install Remedy Single Sign-On, use the instructions in Installing Remedy Single Sign-On. See 7-9-01-Service-Pack-1 for the supported Remedy SSO version.During the external Remedy SSO installation, you are prompted to choose a database type. To use Remedy SSO with BMC Atrium Orchestrator Platform, choose embedded database or Oracle database.

Create the default user, role, and realm

NotePerform these steps only if you are using an external Remedy SSO. If you are installing the embedded Remedy SSO with the BMC Atrium Orchestrator (BAO) Platform upgrade, these steps are completed during the upgrade.
After installing Remedy SSO, you must complete the following tasks before installing BMC Atrium Orchestrator Platform components:
  1. Create a realm named BAOLocal (see Working-with-realms).
  2. 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).
  3. Create a role called AoAdmin (see Creating-and-managing-local-users-and-roles-in-Remedy-Single-Sign-On).
  4.  Assign the aoadmin user to the AoAdmin role  (see Creating-and-managing-local-users-and-roles-in-Remedy-Single-Sign-On).

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*