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 130Number of Views Passcode format error when trying to set a PIN thru a Cisco ASA 383Number of Views Error: Unable to perform pre-login process when trying to login to RSA Authentication Manager 8.x Web Tier Self Service Co… 530Number of Views AuthnContextValidator error when trying to authenticate using RSA Authentication Agent 2.0 for AD FS 95Number of Views Failed to process CT_KIP clientNonceRequest error when trying to import an RSA SecurID software token using CT-KIP for RSA… 424Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?