Please find some common errors which are observed while configuring RA with SSO, listed below
This error occurs when the App/Client configured in SSO server is not matching the ID present in SP metadata.xml generated by Release Automation.
This error occurs when there is an App/Client correct configured but there is on user been associated with that App/Client in SSO server configuration
This error occurs when the SSO server is redirecting fine for the specific user but that user doesn't exist in the list of RA users.
This occurs when you are trying to login to SSO server with username and wrong password.
Release : 6.6, 6.7 or higher
Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER
When you are updated idP from with SP metadata.xml make sure the client/app Id is matching the entityID in the SP metadata.xml generated by Release Automation server.
It will be of format like http://NAC-IP/HOSTAME:PORT/datamanagement/saml/metadata
Please associate the users allowed to access the Client/App configured for RA in SSO server
Create the user used to login in SSO portal in Release Automation server and grant him/her appropriate role in RA
This most often occur when user mistakenly try to use the password which is set while creating user in RA. The login username/password should be matching the one configured in SSO Server