Unsupported content

 

This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

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

For the successful removal of the integration with Remedy AR System, ensure that you have created a system backup before integrating with this product.

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:

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

    Server-Plugin-Alias: ARSYS.AREA.RSSO ARSYS.AREA.RSSO
  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 (in .xml files, comments can be added anywhere in a document. For more information, see the Extensible Markup Language (XML) documentation Open link ):
<plugin>
    <name>ARSYS.AREA.RSSO</name>
    <classname>com.bmc.rsso.plugin.area.RSSOPlugin</classname>
    <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>
    <userDefined>
        <configFile>C:/Program Files/BMC Software/ARSystem/Conf/rsso.cfg</configFile>
    </userDefined>
</plugin>

7. (Optional) If you want to use the AREA LDAP plug-in configuration, add the AREA LDAP reference to the pluginsvr_config.xml file for all the AR services.

8. Restart Remedy AR System server.

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:

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

    1. Review the current value of the following parameter:

      arsystem.authenticator=com.bmc.rsso.plugin.authenticator.RSSOAuthenticator
    2. Update the value of the parameter with the value set in the backed up file:

      arsystem.authenticator=com.remedy.arsys.session.DefaultAuthenticator
    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 (in .xml files, comments can be added anywhere in a document. For more information, see the Extensible Markup Language (XML) documentation Open link ):

    <filter>
        <filter-name>RSSOFilter</filter-name>
        <filter-class>com.bmc.rsso.agent.RSSOFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>RSSOFilter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <listener>
        <listener-class>com.bmc.rsso.agent.RSSOListener</listener-class>
    </listener>
  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.

Troubleshooting

If he 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.

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

Comments

  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