RSA SecurID Access: Identify Java Authentication API version/build
Originally Published: 2010-01-29
Article Number
Applies To
RSA Product/Service Type: Java Authentication API
Issue
There is no version/build identifier present in the SDK
Resolution
- The Authentication Manager API/SDK 8.x logs version information to the debug log.
- Using a text editor, open rsa_api.properties and modify the appropriate values. The sample rsa_api.properties file is located in the \examples\sample folder of the kit.
- The following describes the key-value settings in the properties file:
"RSA_LOG_TO_FILE" set this value to YES
"RSA_LOG_FILE" specify the path to the log file For example: /var/ace/api/my_api_events.log or C:\\WINDOWS\\system32\\my_api_events.log
"RSA_LOG_FILE" specify the path to the log file For example: /var/ace/api/my_api_events.log or C:\\WINDOWS\\system32\\my_api_events.log
- You will find a line similar to the below:
2019-02-01 08:17:54.358 2.1488.2900 [E] info@(#)RSA ACE/Agent Version 8.6.1.0.0[029]
Related Articles
How to build RSA ACE/Server Authentication API application with correct thread library on Sun Solaris Number of Views How to identify the deployed version of the HXTT Text JDBC Driver in RSA Identity Governance & Lifecycle Number of Views How to identify the source of a workflow email in RSA Identity Governance and Lifecycle Number of Views 'java.io.FileNotFoundException: aveksa-version.properties' error running createSchema.sh in RSA Identity Governance & Life… Number of Views Running upgradeJDK.sh issues "ACM is not supported on this version of linux" in RSA VIA Lifecycle & Governance Number of Views
Trending Articles
RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor… Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) How to configure RSA Authentication Manager 8.4 or later to send data to multiple remote syslog servers
Don't see what you're looking for?
