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
How to recreate a replica package set for push in RSA ACE/Server Number of Views How DB-Push Works. Number of Views How to troubleshoot RSA Authenticator app push authentications Number of Views How approval activity behaves when change request items are grouped by category in RSA Identity Governance & Lifecycle Number of Views How RSA Cloud Access Service Push Authentications Work (Approve and Device Biometrics) Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide "No decryption codes were found in the zip file" error when decrypting RSA SecurID tokens Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU
Don't see what you're looking for?
