Logging on to Security console gives "Bad Request 400" after the planned promotion when trying to use friendly alias server name in the URL
Originally Published: 2021-06-03
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4.0
Issue
Edit /opt/rsa/am/utils/resources/ims.properties
You will notice that the last line has an incorrect server name. The alias is pointing to the old server name due to this line.
ims.ssl.client.primary.provider.url=t3s\://<RSA_AM_Primary>.svr.us.mycompany.net\:7022
Cause
Resolution
Workaround
Related Articles
Error "Alias name is too long" while trying to assign an alias to a user in RSA Authentication Manager 8.x 132Number of Views Passcode format error when trying to set a PIN thru a Cisco ASA 383Number of Views AuthnContextValidator error when trying to authenticate using RSA Authentication Agent 2.0 for AD FS 95Number of Views AADSTS50107: Requested federation realm object 'http:/<Identity Router FQDN>/' does not exist when trying to access the Mi… 64Number of Views Error Facts are not available when trying to authenticate using the RSA Authentication Agent 2.0 for AD FS 149Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?