Sample code uses Command Client username, password, provider URL, and JNDI information stored in the clear.
To be invoked by the SDK connection code, the class must be referenced in the CommandClientAppContextOverrides.xml file ConnectionInfoProvider bean definition (instead of com.rsa.command.PropertiesConnectionInfoProvider).
For example:
package com.mycompany.client;
public class MyProvider implements com.rsa.command.ConnectionInfoProvider {
private String propertiesFile = null; //using a file to store the properties
public void setPropertiesFile(String propertiesFile) { //invoked by Spring framework if specified in bean definition
this.propertiesFile = propertiesFile;
}
public String getStringValue(String key) {
String prop = null;
//retrieve (and decrypt) the specified property from propertiesFile
return prop;
}
}
The bean definition in CommandClientAppContextOverrides.xml would then be:
...
<!--
| Override the definition of ConnectionInfoProvider
|-->
<bean name="ConnectionInfoProvider"
class="com.mycompany.client.MyProvider"
lazy-init="false">
<property name="propertiesFile" value="config.properties"/>
</bean>
...
Related Articles
"Invalid Lockbox Configuration File" caused by space after masterpassword in server configuration files 45Number of Views Checkpoint bandwidth report showing incorrect KBytes information 27Number of Views What is procedure to add or reconnect Cisco ESA partner to RSA DLP? 50Number of Views How to make RSA DLP detect encrypted files 21Number of Views AWS IAM Identity Center - SAML My Page SSO Configuration - RSA Ready Implementation Guide 7Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide