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 Web Tier installation fails on Red Hat server - RSA Authentication Manager 8.1 Number of Views Users cannot authenticate successfully when the RSA SecurID token is in either Next Tokencode Mode or New PIN Mode when au… Number of Views RSA Identity Governance & Lifecycle 7.1 installation on Red Hat 6.x fails with the error: Could not start 'default' liste… Number of Views Apache 2.x fails to start after configuring the RSA Authentication Agent 8.0 for Web for Apache Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
