What RSA API agent SDK should a developer be using for RSA AM 8.4.0.13

[DanaBurton1]

We hare having issues with PIN create via the API agent SDK.... what is the API Agent verison we should be using for RSA AM 8.4.0.13 and above

Thanks 

Dana Burton

[RandyBelbin]

Hi Dana,

Moving forward, integrations should use the REST API. You can generate an SDK in the language of your choice by uploading the YAML file to swagger.io.I'll include links to the documentation and some sample code below.

Best,

Randy

RSA SecurID Authentication API Download 

https://community.rsa.com/docs/DOC-108613 

[DanaBurton1]

Thank you Randy

The issue seems to be in the PIN reset... the user has to try two and three times before the PIN or Fixed Passcode in this case is updated on the RSA AM... mind you this is a UDP port 5500 call and I looked at the FW logs and there were no denys and did see the UDP calls... but only saw one request in the RSA AM activity monitor... So question here is - Where does the issue lay in the API in the application or at the RSA AM?

[DanaBurton1]

Thank you Randy

The issue seems to be in the PIN reset... the user has to try two and three times before the PIN or Fixed Passcode in this case is updated on the RSA AM... mind you this is a UDP port 5500 call and I looked at the FW logs and there were no denys and did see the UDP calls... but only saw one request in the RSA AM activity monitor... So question here is - Where does the issue lay in the API in the application or at the RSA AM?

[PiersB]

It probably lays in the network between the Agent and AM. UDP is not a guaranteed delivery protocol. This is true for both Agent authentication requests and server responses. Either of these may be dropped and/or re-transmitted. The server handles duplicate requests returning the previous response (if one is available). The agent handles resending UDP requests to the server if not response is received.

The next level would be to examine things using tcpdump (installed as a part of the AM appliance) and/or a tool like "WireShark" (to examine wire-level protocol packets).