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
- Stop Remedy AR System.
- Navigate to C:\Program Files\BMC Software\ARSystem\Conf and delete rsso.cfg.
Update <AR>/Conf/ar.cfg as follows:
External-Authentication-RPC-Socket:390695 Authentication-Chaining-Mode: 1 Crossref-Blank-Password: TFrom the <AR>/Conf/ar.cfg delete the row that starts with:
Server-Plugin-Alias: ARSYS.AREA.RSSO ARSYS.AREA.RSSONavigate to C:\Program Files\BMC Software\ARSystem\pluginsvr, and delete rsso-area-plugin-all.jar.
- 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
):
<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
Stop Tomcat installed on Mid Tier server.
In <Mid_Tier>/WEB-INF/classes/, delete or rename the following files:
- rsso-agent.properties
- log4j-rsso-webagent.properties (if any)
- rsso-log.cfg
Open the config.properties file that you have backed up, and update it as follows:
Review the current value of the following parameter:
arsystem.authenticator=com.bmc.rsso.plugin.authenticator.RSSOAuthenticatorUpdate the value of the parameter with the value set in the backed up file:
arsystem.authenticator=com.remedy.arsys.session.DefaultAuthenticatorDelete the following row:
arsystem.authenticator.sso.enckey=<the value generated from your backup>
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
):<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>Start Tomcat installed on Mid Tier server.
- 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.
Comments
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 1905 documentation.
Hello, Stefan!
Thank you for the feedback.
These steps were QA tested, and verified by several subject matter experts. Could you, please, let us know if you tried executing it?
Hi, Olga, If it worked, I wouldn't have written it. I always check my clues!
Just read the integration instructions, then you should notice the difference immediately. The deinstallation is incomplete.
Hello, Stefan!
The steps for disintegration were provided by people who tested this procedure.
I will send raise your request with QA team, and update the instruction if they confirm it is not full.
Hello, Stefan!
I consulted with the team again.
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.
I also have same issue on Remedy 1805. I want to disable midtier RSSO in a short time. So I removed the parameter of config file and web.xml and restarted the midtier service , but it didn't work and show 404 error.
Hello!
Thank you for the comment. I will follow up this with the QA team, and get back to you as soon as possible.
Hello, Shih!
We do not have an option to enable integration or disable integration between Mid Tier and Remedy SSO.
Could you, please, review the answer to Stefan Hall above.
Hi @Shih Price - I followed the directions above as well and it was giving me the same 404 error. I followed @Stefan Hall's suggestion as well to remove the lib files. **Note: I did not remove the /lib directory, just the files related to RSSO. Basically, I used the instructions in: https://docs.bmc.com/docs/rsso1908/manually-integrating-remedy-sso-with-bmc-applications-879743213.html (Manually integrating Remedy SSO with BMC applications), and worked backwards. Any files that were manually added, I removed. Despite that - I was still having the 404 / blank screen error. Then I remembered that we had a non-RSSO midtier that was also pointing to the same AR Server, so I decided to try it, and was surprised why it was having the same issue, when RSSO was never installed/integrated on it. Last ditch effort, I decided to just flush the midtier cache on that non-RSSO midtier. Lo and behold, it started connecting properly, asking for login, and finally displaying the ITSM overview console. When I tried to go back to the formerly RSSO-enabled midtier, which I removed RSSO from, now it's working properly. I verified that they're not in the same cluster, nor is the "Sync in cluster" box checked. Crazy..!! Hopefully that helps you out.
Log in or register to comment.