This documentation supports the 20.02 version of Remedy Single Sign-On.To view an earlier version, select the version from the Product version menu.

Disabling TLS checks between the Helix SSO agent and server

You have the option to temporarily disable TLS/SSL checks, if required; for example, for debugging purposes. 


Related topics

Security-planning

Configuring-the-Remedy-SSO-agent
Tomcat SSL configuration

Before you begin

On the application server which has integration with the Remedy SSO agent, import the self-signed certificate used by Remedy SSO server into a truststore.

For details about importing the certificate, refer to the documentation provided by your Java vendor.

To temporarily disable TLS/SSL checks during establishing HTTPS connection

  1. On the application server, open the rsso-agent.properties file.

  2. Add the following string to the rsso-agent.properties file:

    com.bmc.rsso.tls.disable.checks=true
  3. Save the changes, and then restart the application server.
  4. If you have an integration with Remedy AR System, perform the following steps to configure AREA plugin:
    1. On the Remedy AR System server, open the rsso.cfg file available in \ARSystem\Conf directory.

    1. Edit the following string as follows:

       com.bmc.rsso.tls.disable.checks=true
    2. Save the changes. 
  2. To enable the TLS/SSL checks, make sure you reset the value of the com.bmc.rsso.tls.disable.checks parameter in the rsso-agent.properties and rsso.cfg files to false.

Where to go from here

If you have problems establishing the HTTPS connection, review Troubleshooting-common-errors-and-issues.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*