RSA ACE/Agent for Web gives access to protected pages when correct passcode is used
Originally Published: 2000-01-19
Article Number
Applies To
RSA ACE/Agent for Windows
Issue
"PASSCODE Accepted" in ACE/Server log
Error: "Cookie rejected. Cookie failed MD5 test." in Windows event log
Resolution
These permissions are viewed and modified using the 'REGEDT32' utility
(WARNING from Microsoft: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.)
Go to the registry key "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\w3svc"
There should be three sets of permissions:
Administrators Full Control
Everyone Special Access
SYSTEM Full Control
These setting should exist on the "w3svc" key and all existing subkeys
If the permissions are wrong, then they can be added back in and the option to "Replace Permission on Existing Subkeys" selected.
Related Articles
RSA Identity Governance and Lifecycle fails to start with error "Task exists with the given name " 32Number of Views Update version is not correct when attempting to perform an upgrade 28Number of Views AM8.x Migration Export Utility is giving an incorrect error message on a SP4 system 12Number of Views RSA Authentication Agent 7.3.3 for Windows prompt does not appear after the first reboot of Windows 10 when McAfee SafeBoo… 140Number of Views RSA Authentication Agent for Microsoft Windows Is Not Authenticating Against the Correct Contact List 45Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?