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

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

Removing Remedy SSO integration from Remedy AR System and Remedy Mid Tier

To remove the integration between Remedy Single Sign-On and Remedy AR System, manually perform the steps described in this topic.


You can successfully remove integration between Remedy SSO and Remedy AR System only if you have created a system backup before integrating with Remedy AR System.

To remove the integration between Remedy SSO and Remedy AR System server 

  1. Stop Remedy AR System.
  2. Navigate to C:\Program Files\BMC Software\ARSystem\Conf and delete rsso.cfg.
  3. Update <AR>/Conf/ar.cfg as follows:

    Authentication-Chaining-Mode: 1 
    Crossref-Blank-Password: T
  4. From the <AR>/Conf/ar.cfg delete the row that starts with:

  5. Navigate to C:\Program Files\BMC Software\ARSystem\pluginsvr, and delete rsso-area-plugin-all.jar.

  6. In ARSystem\pluginsvr\, open pluginsvr_config.xml, and comment out the following rows:

        <pathelement type="location">C:/Program Files/BMC Software/ARSystem/pluginsvr/rsso-area-plugin-all.jar</pathelement>
        <pathelement type="location">C:/Program Files/BMC Software/ARSystem/pluginsvr/gson-2.3.1.jar</pathelement>
        <pathelement type="location">C:/Program Files/BMC Software/ARSystem/pluginsvr/slf4j-api-1.7.25.jar</pathelement>
            <configFile>C:/Program Files/BMC Software/ARSystem/Conf/rsso.cfg</configFile>
  7. Restart Remedy AR System server.


    If the 1053 error (The service did not respond to the start or control request in a timely fashion) is displayed, wait for several minutes. The service will start in some time.

To remove the integration between Remedy SSO and Remedy Mid Tier

  1. Stop Tomcat installed on Mid Tier server.

  2. In <Mid_Tier>/WEB-INF/classes/, delete or rename the following files:

    • (if any)
    • rsso-log.cfg
  3. Open the file that you have backed up, and update it as follows:

    1. Review the current value of the following parameter:

    2. Update the value of the parameter with the value set in the backed up file:

    3. Delete the following row:

      arsystem.authenticator.sso.enckey=<the value generated from your backup>
  4. In <Mid_Tier>/WEB-INF/web.xml, comment out the following rows:

  5. Start Tomcat installed on Mid Tier server.

  6. In a browser window, log in to AR System to validate access to AR System/ Mid Tier.

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


  1. Stefan Hall

    the description does not fit to the installation instructions. Please adapt the documentation and the deletion of libs to the installation.

    Of course, this also applies to the 1908 documentation.

    Aug 28, 2019 02:34
    1. Olga Kutetska

      Hello, Stefan!

      I suppose you have seen the reply to the same comment in 1905. Just in case, you have not, I am duplicating it here:

      The steps provided in this topic work if you perform integration, and then you remove integration. If after integration with Remedy SSO, you performed some additional steps, such as integration with some other products, you must perform some additional manual steps.

      This topic is for general understanding of the process of removing integration with Remedy SSO, and may not fit specific use cases.

      We are not recommending to delete libs from the  <Mid_Tier>/WEB-INF/lib because these libs can be used by some other integrated products with which you do not want to remove the integration.

      Mar 17, 2020 06:48