Common errors and issues
Following table lists down the errors and issues that you may encounter with Remedy Single Sign-On. A corresponding workaround or a fix is given with details next to the problems.
Remedy Single Sign-On server is not started
Configuration issue during start up
|After you are successfully authenticated by Identity Provider (IdP), the login page reappears.||Authentication cookie is not respected by the browser|
Server exception, stack trace includes reference to the com.bmc.arsys.api.session
Mid Tier authenticator configuration issue
Verify the Mid Tier authenticator configuration file to define the RSSO authentication plugin.
|623 AR Error|
RSSO AREA plugin configuration
|In HA mode, server exception, stack trace includes reference to the ‘com.bmc.rsso.sdk.token.CookieTokenManager|
RSSO agent can’t connect to RSSO server to obtain piece of configuration
When using SAML-based IdP, server exception with the
Note: Stracktrace refers to the diagnostic information in the log file that indicates which was the Java stack when the exception was raised.
|Time at the Remedy Single Sign-On server and IdP server is out of sync|
Synchronize the time across the servers
|Remedy Single Sign-On logs do not include diagnostic information|
Log records with the levels of ‘TRACE’ and ‘DEBUG’ are filtered by the ‘Logging level’ setting