This documentation supports the 19.02 version of Remedy Single Sign-On.

To view an earlier version, select the version from the Product version menu.

Integrating Remedy SSO with BMC Digital Workplace

This topic describes how to configure the integration between Remedy Single Sign-On and BMC Digital Workplace.

Based on your organization’s requirement, you can configure any of the authentication methods to authenticate end users for various BMC applications.

As an administrator you can integrate Remedy SSO with BMC Digital Workplace. After the integration, you can configure the required protocol for authentication. BMC does not support the Kerberos authentication for mobile apps, but you can configure the Kerberos authentication for web apps.

Remedy Single Sign-On authentication applies to both the universal client and to mobile applications. When a user logs in to on a mobile device, the user is prompted to enter the host name and port. If the server has SSO enabled, the mobile client opens a browser to the SSO login page. The SSO server sets the SSO cookies after authentication on to the device browser. When the user relaunches the application, if the cookies are not expired, the mobile client displays the application. If the cookies are expired, the user is shown the login page again for authentication.

Before you begin

  • Install Remedy Single Sign-On
  • Configure a realm for BMC Digital Workplace. Remedy SSO server and BMC Digital Workplace server require the same domain. Otherwise, deploying the Remedy Single Sign-On agent will not work.
  • Create the file.

To integrate Remedy SSO with BMC Digital Workplace

For clusters, complete the following procedure for each BMC Digital Workplace server.

  1. Start the DWPTomcat service.
  2. Make sure Single Sign-On integration is enabled on BMC Digital Workplace database table.
  3. To enable the integration, perform either of the followings steps:

    • Go to the BMC Digital Workplace  DWP_System.TENANT database table, and validate if the value of the SAML_AUTHENTICATION is set to 1.

      To update the SAML_AUTHENTICATION, run the following query:

      UPDATE DWP_System.TENANT  
    • Run the following command using Java 1.8 or later:

      java -jar <DigitalWorkplace_path>/tenant-config/tenant-config-<DigitalWorkplace_version>-jar-with-dependencies.jar updateTenant -server http://<DigitalWorkplaceServer>:<PortNumber>/dwp -username <DigitalWorkplace_Super_Admin_username> -password <DigitalWorkplace_Super_Admin_password> -tenantName <TenantName> -hostname localhost -samlAuthentication true
  4. Restart the Tomcat service.

Was this page helpful? Yes No Submitting... Thank you


  1. Leonard Warren

    I believe step 2 is not an actual step but a verification statement. I was confused when I first read it because I was wondering how to ensure Single Sign-On integration is enabled and then step 3 takes me through it. I would suggest changing the second step to a verification statement and change the remaining two steps to 2 and 3.

    Aug 08, 2019 10:34
    1. Olga Kutetska


      Thank you for your feedback. I have modified the document, and moved the step to the Before you begin section. The update will be published next week.

      Aug 09, 2019 04:11