Safely backout of a failed configuration push in RSA Web Threat Detection
Originally Published: 2016-07-20
Article Number
Applies To
RSA Product/Service Type: Mitigator
RSA Version/Condition: 4.6 - 6.0
Issue
The customer needs to restore the system and roll-back the change.
Resolution
https://,your-wtd-system>:4448/safemode
2. This will display the following message-- (unless you never saved UIServer Configuration)
-----------------------
Safe mode allows UIServer to come up with a previously-saved UIServer configuration file.
Last saved at: Fri Jul 8 16:37:23 2016.
Please click Ok to proceed
--------------------------
3. Click the OK button and it will bring your configuration back to the previous configuration.
Notes
The reason for the failure to push could be due to wrong syntax of the config file, or an attribute syntax, but now you are able to troubleshoot the cause.
Related Articles
Delinea - SAML Relying Party Configuration - RSA Ready Implementation Guide 9Number of Views How DB-Push Works. 38Number of Views How to recreate a replica package set for push in RSA ACE/Server 36Number of Views Thycotic Secret Server 10.6- RSA Ready SecurID Access Implementation Guide 10Number of Views RSA Access Manager integration with eRoom is not working. 15Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?