Authentication error for a challenged user with RSA Authentication Manager using REST protocol for RSA Authentication Agent 8.x for PAM
Originally Published: 2019-06-21
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for PAM
RSA Version/Condition: 8.x
Platform: Linux
Issue
- When the challenged users trying logging into the machine through SSH they are getting below error.
- After enabling the DEBUG for the REST protocol, the /var/ace/log/mfa_rest.log shows either of following errors:
INFO (../src/ConnectionHandler/ConnectionHandler.cpp:355) - Connecting to Server: https://amv84p.example.com:5555/mfa/v1_1/authn
ERROR (../src/ConnectionHandler/ConnectionHandler.cpp:359) - Failed to connect.Curl error code: 6
or
INFO (../src/ConnectionHandler/ConnectionHandler.cpp:355) - Connecting to Server: https://amv84p.example.com:5555/mfa/v1_1/authn
ERROR (../src/ConnectionHandler/ConnectionHandler.cpp:359) - Failed to connect.Curl error code: 28
Cause
Curl error code 6
The error displays on the machine where the Authentication Agent for PAM is installed when the agent is unable to resolve the Authentication Manager server hostname.Curl error code 28
The error displays on the machine where the Authentication Agent for PAM is installed when the agent is not able get the authentication response from the Authentication Manager servers before it timeouts.Resolution
For Curl error code 6
- In client system, where pam agent is installed, Login as root user and edit hosts file. Run below command for that.
vi /etc/hosts
- Enter the IP addresses and fully qualified domain names of the primary and replica Authentication Manager servers. For example,
192.168.1.10 amv84p.example.com #AM primary
102.168.1.11 amv84r.example.com #AM replica
102.168.1.11 amv84r.example.com #AM replica
- Save the changes.
- Open an SSH session and try to authenticate with a challenged user. This time it will prompt for passcode.
- Enter the RSA passcode and verify that the authentication succeeds.
For Curl error code 28
- On a client system, where the Authentication Agent for PAM is installed, login as the root user.
- Navigate to /var/ace/conf on the Linux server and edit the mfa_api.properties file.
- Change the CONNECT_TIMEOUT value to 120 and the READ_TIMEOUT value to 160.
- Save and close the file.
- Open an SSH session and try to authenticate with a challenged user. This time it will prompt for passcode.
- Enter the RSA passcode and verify that the authentication succeeds.
Related Articles
Change the Timeframe for Using REST Protocol Authentication Agent Credentials 17Number of Views Managing REST Protocol Authentication Agent Credentials 63Number of Views Deploying an Authentication Agent that Uses the UDP 34Number of Views Deploying an Authentication Agent That Uses the REST Protocol 72Number of Views Disable RSA SecurID Authentication API 72Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?