Configure Single Sign-On between HCM ARA and Operations Orchestration

If Single Sign-On was enabled during installation of HCM ARA, Single Sign-On can be configured between HCM ARA and Operations Orchestration. Configuring Single Sign-On allows you to launch Operations Orchestration from the Codar Console without having to log in to Operations Orchestration.

HCM ARA provides an out-of-the-box user (admin) and password (cloud) and, earlier in this guide, you configured an internal user for Operations Orchestration with the same user name and password. When Single Sign-On is configured between HCM ARA and Operations Orchestration, this user can be used for single sign-on. That is, if you are logged in to HCM ARA as the admin user, you can launch Operations Orchestration from the Codar Console and not have to log in to Operations Orchestration.

You can also configure LDAP users for single sign-on. In order to enable single sign-on for LDAP users, you must either configure HCM ARA and the embedded Operations Orchestration to use the same LDAP source or, if HCM ARA and the embedded Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the HCM ARA user must be assigned to the HCM ARA Administrator or Service Operations Manager role and the embedded Operations Orchestration user must be assigned any role that allows flows to be viewed.

Note To use Single Sign-On between HCM ARA and Operations Orchestration, the systems on which HCM ARA and Operations Orchestration are installed must be in the same domain.

Enable Single Sign-On

To configure and enable Single Sign-On on Operations Orchestration, complete the following steps:

1. Log in to Operations Orchestration Central.

2. Click the System Configuration button.

3. Select Security > SSO.

4. Select the Enable checkbox.

5. Enter the InitString. The initString setting for HCM ARA and Operations Orchestration must be configured to the same value. In HCM ARA, initString is configured in the crypto element in the CSA_HOME\jboss-as\standalone\deployments\csa.war\WEBINF\hpssoConfiguration.xml file. The initString value represents a secret key and should be treated as such in your environment (this string is used to encrypt and decrypt the LWSSO_COOKIE_KEY cookie that is used to authenticate the user for single sign-on).

6. Enter the Domain. This is the domain name of the network of the servers on which HCM ARA and Operations Orchestration are installed.

7. Click Save.

Configure LDAP Users for Single Sign-On

In order to enable single sign-on for LDAP users, you must either configure HCM ARA and Operations Orchestration to use the same LDAP source or, if HCM ARA and Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the HCM ARA user must be assigned to the HCM ARA Administrator or Service Operations Manager role and the Operations Orchestration user must be assigned any role that allows flows to be viewed.

To configure LDAP for Operations Orchestration, complete the following steps:

  1. Log in to Operations Orchestration Central.
  2. Click the System Configuration button.
  3. Select Security > LDAP.
  4. Enter the information to configure LDAP.
  5. Click Save.

Send Help Center feedback