RSA SecurID Authentication - REST API

[JimmyTran1]

Hi,

I'm looking to implement RSA authentication using the REST API. I was able to make the call against AM but it's returning back with -

"credentialValidationResults":[{"methodId":"SECURID","methodResponseCode":"FAIL","methodReasonCode":"VERIFY_ERROR","authnAttributes":[]}],"attemptResponseCode":"FAIL","attemptReasonCode":"VERIFY_ERROR","challengeMethods":{"challenges":[]}

I'm pretty certain I'm putting in the correct subjectId (username) and the generated token after I entered in my PIN. I looked through the PDF documentation but couldn't find anything related to this error.

Any idea?

Thanks

[TedBarbour]

Hi Jimmy Tran - did you check for authentication activity messages at the Authentication Manager?

Also, for troubleshooting purposes you might enable the user you are testing with to use a simple fixed passcode.   This would help ensure you are correctly providing a valid passcode.

[JimmyTran1 · Accepted solution]

Thanks Ted. Unfortunately, I did not have access to those logs. I had to get my systems team involved in the troubleshooting process. We were able to resolve it with tech support help. The issue was related to the clientId field, it had to have FQDN.

[PiersB]

You are correct, the "clientId" must be a named agent in the database as outlined in the RSA SecurID Authentication API Developer's Guide.

Just to clarify, although the "clientId" has to contain an agent name, it is not required to contain the FQDN of the agent. The client calling the API may choose to provide a logical name like "VPN Cluster Node" instead and use that logical name on all appropriate client systems. Agents are no longer required to have an IP address and can be a "logical" agent for access control purposes.