- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue with upgrade to RSA Authentication API 8.5
I'm currently working on upgrading our SecurID integration with RSA Authentication API 8.5 and have ran into an issue with authentication. The logs are indicating an error with regards to empty key which I'm not sure what it's referring to. The specific error is as follows,
2017-04-20 14:20:31,381 tid:luxzlUOoKT6HlNdAoJxNoInLKWM ERROR [com.rsa.authagent.authapi.v8.logger.b] Error in processing Authn request: Empty key
2017-04-20 14:20:31,381 tid:luxzlUOoKT6HlNdAoJxNoInLKWM ERROR [com.rsa.authagent.authapi.v8.logger.b] Error in initial AuthnReq/Rsp for serverTime.Error in processing Authn request: Empty key.
It looks like the agent was able to connect successfully and exchange configuration as there are some config and cert files being generated but I'm just not sure about the possible reasons for this particular error, any help would be appreciated in that regards. Thanks
- Tags:
- Community Thread
- Discussion
- Forum Thread
- Integration
- Integrations
- RSA SecurID
- RSA SecurID Access
- RSA SecurID Integration
- SecurID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Yasir - have you followed the Developer's Guide section "Configure Message Key Negotiation"?
Also, note that the latest version of the API is 8.6.
Ted
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend that you https://community.rsa.com/docs/DOC-1294 and open a ticket so that you can work with a technical support resource to address the error.
Regards,
Erica
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should also add that RSA just released a new RSA SecurID Access RSA SecurID Authentication API that allows you to develop clients that process multifactor, multistep authentications through RSA Authentication Manager and the Cloud Authentication Service. Note that this new API requires Authentication Manager version 8.2 Service Pack 1 or later.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the feedback, it turned out to be node secret related. I reset the secret and it seems to be working now..
