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

To view the latest version, select the version from the Product version menu.

Integrating Remedy SSO with BMC Digital Workplace

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

Based on your organization’s requirement, you can configure any of the authentication methods to authenticate the 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 and configure realms. For more information, see the  Remedy Single Sign-On  online documentation.
  • Install BMC Digital Workplace.
  • Verify that access to the Remedy SSO servers and the BMC Digital Workplace server requires 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, go to the BMC Digital Workplace database table 'DWP_System.TENANT' and make sure that the value of the 'SAML_AUTHENTICATION' column is True(1).

    a. Run the following SQL query to update the SAML_AUTHENTICATION column:


    b. Run the following command by using Java 1.8 or later:

    java -jar <DigitalWorkplace_path>/tenant-config/tenant-config- updateTenant -server http://<DigitalWorkplaceServer>:<PortNumber>/dwp -username <DigitalWorkplace_Super_Admin_username> -password <DigitalWorkplace_Super_Admin_password> -tenantName 000000000000001 -hostname localhost -samlAuthentication true

  4. Restart the Tomcat service.

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


  1. Mark Wychowski

    Why are the notes for under the section for 'SAML_AUTHENTICATION' column?

    Nov 12, 2018 06:22
    1. Vrishali namdev Galinde

      Hi Mark,

      Thank you for pointing this out. I will make the necessary changes.

      Thanks & Regards,


      Nov 12, 2018 10:38