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.

Troubleshooting common errors and issues

The following table describes errors and issues that you may encounter with Remedy Single Sign-On. 


Problem with handshake while using an HTTPS connection

The certificate on the Remedy SSO is a self-signed certificate or is signed by a trustworthy CA.

  1. Check that the Remedy SSO server certificate is valid.

  2. If you have a self-signed certificate, make sure that you have imported it to the Java truststore.

Remedy SSO server does not start

Configuration issue during start up

Check the catalina.log (located in CATALINA_HOME/logs) for any issues related to the Remedy SSO web application.

Check the rsso.log file (located in CATALINA_HOME/logs) for exceptions related to the database connectivity (for example, the JDBC URL or the database user login and password).

Check the rsso.log file for the exceptions related to the marshalling of the configuration data.
Note: Marshalling refers to automatic creation of the Java objects from the XML source using the JAXB approach.

Server exception (stack trace) includes a reference to the com.bmc.arsys.api.session

Configuration issue with Remedy Mid Tier authenticator

Verify the BMC Remedy Mid Tier authenticator configuration file to define the Remedy SSO authentication plugin. For more information, see Manually integrating Remedy SSO with BMC applications.
623 AR Error

Remedy SSO AREA plugin configuration issue

Check the following:

General AREA configuration

Configuration of the plugin server (ASSO-related info is commented)

Corresponding property points to the Remedy SSO base URL in the rsso.cfg file

For more information, see Manually integrating Remedy SSO with BMC applications.

In HA mode, the server throws an exception. The stack trace includes a reference to com.bmc.rsso.sdk.token.CookieTokenManager.

Remedy SSO agent cannot connect to the Remedy SSO server to obtain a piece of configuration.

Verify the load balancer settings about the HTTP redirection (3xx status after agent request is unwanted).

Correct the Remedy SSO server URL in the agent connection. For more information, see Manually integrating Remedy SSO with BMC applications.

When using SAML-based IdP, a server exception with the text, "Failed to validate … condition," is displayed in the stacktrace.

Note: Stracktrace refers to the diagnostic information in the log file that indicates which Java stack was used when the exception was raised.

The times on the Remedy SSO server and IdP server are out of sync.

Synchronize the time across the servers.

When using LDAP-based IdP, the following error is recorded in the Remedy SSO logs:

SEVERE [LDAP: error code 4 - Sizelimit Exceeded] 

The maximum number of entries that the LDAP server can process in one call is less than the number of user entries the Remedy SSO server requests in a single call.

To extend the default limit of 2000 of entries, increase the Page Size value for LDAP authentication. For more information about how to do this, see Configuring LDAP authentication.

Remedy SSO logs do not include diagnostic information.

Log records with the levels of TRACE and DEBUG are filtered by the Logging level setting.

Check the logging level in the Remedy SSO Admin Console. For more information, see Configuring server settings for BMC Remedy SSO

Check the log configuration file (RSSOInstallFolder/WEB-INF/classes/

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