RSA Via Lifecycle and Governance Salesforce Account Data Collector does not allow configuration without a "Security Token"
Originally Published: 2016-03-23
Last Modified: 2022-06-20
Article Number
000064564
Applies To
RSA Product Set: Identity Management and Governance
RSA Version/Condition: 6.9.1, 7.0
 
Issue

When configuring a new Salesforce Account Data Collector the field "Security Token" field is mandatory. This prevents customers from leveraging an alternate method of authentication based on Salesforce IP filtering that does not require a token.

If a null value is entered for the Security Token, the following error is generated.

Collector test failed: 
com.aveksa.server.runtime.ServerException: Test request failed with response: 
com.aveksa.server.runtime.ServerException: com.aveksa.common.ConnectException: Invalid Credentials. 
Caused by com.aveksa.common.DataReadException: Error occured while connecting Salesforce instance. 
Caused by java.net.ConnectException: Connection refused Caused By Stack com.aveksa.common.ConnectException: 
Invalid Credentials at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:140)

 
Cause
The Secure Token field was inadvertently made mandatory in 6.9.1 and 7.0 release versions. 
Resolution
This issue is resolved in the following patches and all versions and patches later than the following:
  • RSA Aveksa 6.9.1 P12
  • RSA Via Lifecycle and Governance 7.0 P03
  • RSA Via Lifecycle and Governance 7.0.1

 
Workaround
There are no known work arounds to this issue for customers wishing to use SalesForce trusted IP filtering.  Customers can use the alternate means of authentication for SalesForce that requires a Secure Token. 

Related Articles

Trending Articles

Don't see what you're looking for?