000021533 - How to upgrade RSA ACE/Server API/SDK code from 5.2 to 6.0

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021533
Applies ToRSA ACE/Server 5.2 Administration API
RSA Authentication Manager 6.0 Administration API
RSA ACE/Server Administration API
IssueHow to upgrade RSA ACE/Server API/SDK code from 5.2 to 6.0
What are the differences between 5.2 and 6.0 Admin API
CauseWhen RSA ACE/Server 5.2 is upgraded to RSA Authentication Manager 6.0, the upgrade procedure clearly presents which steps are required. What is less obvious is what should occur for any application written to use the Administration API (written in either C or TCL).
ResolutionRSA Authentication Manager 6.0 API has one new function Sd_SetUserOAWindowsPW() which is used for specific SecurID for Windows functionality.  Also, some existing function calls have been modified for similar reasons.

In all known instances, no changes need be made to any existing API code. However, the old custom code must be re-linked with the new API files.

Where changes have been made to a function call (such as Sd_AddAgentHost), they have been made such that they will be backward compatible with the older code, for example:

Sd_AddAgentHost() has a parameter 'agentHostFlags', where the older 5.2 API had the following definition:


where values could be combined to indicate the available functionality of the Agent Host. With the RSA Authentication Manager 6.0 API, two additional values are supplied:

    CLIENT_ALLOW_OA (=16),

Therefore, existing code will continue to work correctly (after re-linking) with the RSA Authentication Manager 6.0 libraries.

Where a programmer wishes to make use of RSA Authentication Manager 6.0 functionality (for example, creating an Agent Host that allows offline authentication), then minor changes would be required. RSA Security advises against attempting to run an existing application linked with 5.2 libraries against the 6.0 Authentication Manager as this could have unforeseen results.
Legacy Article IDa23467