Knowledge Article
Remedy Single Sign-On: Error while accessing CMDB/SMARTIT/DWP "RSSO Server is not Responding or is not available. Please contact your Administrator "
RSSO: Error while accessing CMDB/SMARTIT/DWP "RSSO Server is not Responding or is not available. Please contact your Administrator "
BMC Helix Single Sign On
BMC Helix Single Sign On
RSSO 19.x or higher version
After Integrating RSSO with AR Server/SmartIT/DWP the following error can be observed: |
Configuration issues
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. The Error is mostly seen because of discrepancy between the rsso.cfg and rsso-agent.properties file and should be resolved by following the below steps: 1. Check if rsso-osgi.jar file (located on the ARServer) is present in ARSystem/deploy folder. 2. Open your "rsso-agent.properties" file from \BMC Software\ARSystem\Conf\ 3. Verify if the "SSO-SERVICE-URL" is correctly pointing to your RSSO Server URL You can compare the value with your entry in the rsso.cfg file e.g. sso-service-url=http://<RSSOServerName>.<Domain>:<PORT>/rsso 4. Verify that your URL is not ending with "/" (e.g. http://<RSSOServerName>.<Domain>:<PORT>/rsso/) 5. If you are using the SSL protocol try enabling the parameter "com.bmc.rsso.tls.disable.checks=true" and restart the AR Server service (this option can't be changed at run time). For SmartIT/DWP enable that parameter in the Tomcat and application "rsso-agent.properties" files and restart the Tomcat services. Network issues: 6. Check if there are no Firewall policies blocking the connection 7. Check if you are able to reach the RSSO DNS URL from the AR Server In case of an RSSO LB it should have communication open with the ARServer jetty server and configured port. Verify arserverd.config files in ARSystemHome/, You may have protocol differences which are being allowed on ARServer, or also check if any proxy is set up at the same time also verify java security file to check disabled and allowed TLS protocols (this is mainly for open JDK) BOOT order after integration RSSO needs to be able to read the AR configuration on boot. To ensure this we need to start the services in the following order: RSSO AR All other applications related to AR (for example MidTier, SmartIT, DWP, etc) If all the above steps do not resolve the issue then follow the below document to integrate RSSO with jetty Server (part of the ARServer install): https://docs.bmc.com/docs/ars2002/manually-integrating-remedy-single-sign-on-with-jetty-server-935091371.html |
Attachment(s):