New PIN Mode and Next Tokencode Mode not working from the web pages using RSA Authentication Agent for Web for Apache on Red Hat Enterprise Linux
Originally Published: 2015-09-08
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Web for Apache
RSA Version/Condition: 7.x, 8.x
Issue
- New PIN Mode is working correctly when using acetest from the command line.
- Trying New PIN Mode from the SecurID login web page gives the following exception:
103: Response to the New PIN Request took too long. Please try again.
Cause
Resolution
Apache is being run by daemon, so the VAR_ACE directory should be owned by daemon. With the command below, change the owner of the VAR_ACE directory recursively. In this example, VAR_ACE is set to /var/ace:
chown -R daemon:daemon /var/ace
This command will resolve issues with both New PIN Mode and Next Tokencode Mode.
Related Articles
RSA Identity Management and Governance SSLHandshakeException when using a custom Java workflow node on Red Hat Enterprise … Number of Views ACS exception that occurs when signing is used along with POST and Redirect bindings Number of Views SELinux support for RSA Authentication Agent 7.1.0.1 for PAM on Red Hat Enterprise Linux Number of Views New PIN Mode and Next Token Mode fail on Cisco VPN 3000 Concentrator with RSA ACE/Server Number of Views Web Tier installation fails on Red Hat server - RSA Authentication Manager 8.1 Number of Views
Trending Articles
RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor… RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) Troubleshooting RSA SecurID Access Application Portal unsuccessful logon message due to a bad identity source bind RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
