000017266 - Third-party product integration with RSA Authentication Manager 8.x - Invalid file size of 2 770 bytes

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

Article Content

Article Number000017266
Applies ToRSA Authentication Manager 8.0
RSA Authentication Manager 8.1
VMware View 5.x
Avaya VPN Gateway 3000 Series
configuration record (sdconf.rec)
IssueThird-party product integration with RSA Authentication Manager 8.x using the Native SecurID protocol.
Invalid file size of 2,770 bytes. The RSA Configuration file size must be between 512 and 2,048 bytes.
CauseRSA Authentication Manager 8.0 and RSA Authentication Manager 8.1 generates a configuration record (sdconf.rec) which has a larger file size than 2,048 bytes.
Resolution

This is a known issue by RSA and some third-party vendors using an older RSA Authentication Agent API embedded in their products.


 


Customers are advised to use the EMC Solution Gallery located at URL https://gallery.emc.com/community/marketplace/rsa?view=overview and/or the RSA Ready Community at URL https://community.emc.com/community/connect/rsaxchange/rsa-ready to search for RSA SecurID implementation guides written where the third-party product was certified with RSA Authentication Manager 8.1.


 


Look for the Known Issues section at the back of the implementation guide for workarounds relating to the configuration record (sdconf.rec).


 


Customers can also contact the vendor of the third-party product to check if the vendor has any knowledge article relating to this issue.


 


Examples:


 


 



 

 


If the third-party product supports RADIUS then please consider using RADIUS to send authentications to RSA AUthentication Manager 8.1 before contacting RSA Customer Support if you are unable to find an appropriate RSA SecurID Implementation Guide.

Legacy Article IDa68090

Attachments

    Outcomes