Integration with Remedy Single Sign-On

Remedy Single Sign-On (Remedy SSO) is an authentication system that supports various authentication protocols such as LDAP and provides single sign-on for users of BMC products. For more information about Remedy Single Sign-On, including installation and configuration, see Remedy Single Sign-On overview in the Remedy Action Request System 19.05 online documentation.

Integrating BCM with Remedy SSO enables Remedy with Smart IT technicians to remote control BCM managed endpoints through the BCM browser-based console.

The Remedy SSO administrator typically provides the parameters needed to apply Remedy SSO settings in BCM. As a BCM administrator, ensure that the mandatory settings are met to ensure a successful integration.

To integrate with Remedy SSO, a BCM administrator must configure Remedy SSO parameters in the BCM console. After successfully configuring Remedy SSO with BCM, the Remedy with Smart IT administrator gets access to the BCM browser-based console to search for and remote control BCM managed devices.

Before you begin

As a BCM administrator who is integrating BCM with Remedy SSO, ensure that the following settings are met:

• Remedy SSO parameter details
  • RSSO URL
  • Realm
  • Certificate Authority
  • Server Certificate

Mandatory settings

• The minimum supported version of Remedy SSO is 9.1.01 and later.
• The BCM master and the Remedy SSO server must be in the same domain. For example, if the BCM master server domain name is bcm.calbro.com, then the Remedy SSO domain name must be rsso.calbro.com.
• BCM and the Remedy SSO server must use the same LDAP server. Otherwise, BCM is unable to check user permissions even if the user has successfully logged in through Remedy SSO.
• The BCM master server must have a reservation in DNS and must be accessed using that DNS name; otherwise, the integration fails and the following message is displayed: Forbidden request! Goto url is wrong.
• The same user must be present on both Remedy SSO and BCM master server; otherwise, the integration fails. For example, if AllenBrooks is authenticated through Remedy SSO, then a user AllenBrooks should be present on the BCM master server as well.

Considerations for configuring certificates

Communication between BCM and Remedy SSO can take place only over secured protocol (HTTPS). To enable communication by using HTTPS, you must obtain the HTTPS certificate from the Remedy SSO server.

You can supply a CA bundle that is trusted by your organization, pin the certificate downloaded from Remedy SSO, or use both.

A pinned certificate is more secure than a CA bundle; however, pinned certificates require more frequent renewal. BMC recommends that you use both a pinned certificate and a trusted CA bundle to verify the identity of the Remedy SSO server.

Remedy SSO parameters

As a BCM administrator, you must get the following settings from a Remedy SSO administrator. The following parameters are required to configure Remedy SSO with BCM.

To configure BCM to integrate with Remedy SSO

As a BCM administrator, you need the required parameters to configure Remedy SSO in BCM.

To apply the Remedy SSO settings, perform the following steps: 

1. In the BCM console, go to Global Settings > System Variables.
2. In the RSSO tab, enter the parameter values.
   1. Enable RSSO
   2. RSSO URL
   3. RSSO Realm ID
   4. Product Identifier
   5. RSSO Token revalidation period
   6. Certificate Authority
   7. Server Certificate
3. Click OK.

Troubleshooting

Next step

Connect to the BCM browser-based console using Remedy SSO credentials