Federated Salesforce Account Collector fails with 'Invalid Credentials' in RSA Identity Governance & Lifecycle

[#1]

Article Number

000039042

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
 

Issue

The test of an Account Collector configured as data source type Federated Salesforce (Collectors > Account/Entitlement Collectors > {Collector name} > Test button) fails with the following error:
 

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: 
Response with HTTP Status Code 400 Caused By Stack com.aveksa.common.ConnectException: 
Invalid Credentials at com.aveksa.collector.federatedsalesforce.FederatedSalesforceCollectorDriver.
testConnection(FederatedSalesforceCollectorDriver.java:142) at
com.aveksa.collector.federatedsalesforce.adc.FederatedSalesforceAccountDataReader.testConnection

The following errors are logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log😞
 

07/24/2018 12:38:12.766 ERROR (ApplyChangesRegularThread-20338) [com.aveksa.collector.federatedsalesforce.FederatedSalesforceCollectorDriver] Invalid Credentials
com.aveksa.common.DataReadException: Login request failde with status code: 500
	at com.aveksa.collector.federatedsalesforce.FederatedSalesforceCollectorDriver.getSession(FederatedSalesforceCollectorDriver.java:206)
	at com.aveksa.collector.federatedsalesforce.FederatedSalesforceCollectorDriver.testConnection(FederatedSalesforceCollectorDriver.java:139)
	at com.aveksa.collector.federatedsalesforce.adc.FederatedSalesforceAccountDataReader.testConnection(FederatedSalesforceAccountDataReader.java:50)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectData(AccountDataCollector.java:351)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collect(AccountDataCollector.java:302)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectTestData(AccountDataCollector.java:277)
	at com.aveksa.client.datacollector.framework.DataCollectorManager.collect(DataCollectorManager.java:533)
	at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:204)
	at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:102)
	at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:60)
	at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67)
	at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:377)
	at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:364)
	at com.aveksa.client.component.communication.ChangeListHandler.access$300(ChangeListHandler.java:58)
	at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:275)
	at java.lang.Thread.run(Thread.java:748)
07/24/2018 12:38:12.767 ERROR (ApplyChangesRegularThread-20338) [com.aveksa.client.datacollector.framework.DataCollectorManager] DCM281: Collection Failed: CollectionFailedEvent[cmi = CollectionMetaInfo[{ID=42, run_id=1532450292053, collector_id=7, test-run=true, collector_name=Salesforce TST ADC, data_size=0, data_file=/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempb1f888bd920a64cb/content-8607f2030f58c818/contents/aveksa.war/WEB-INF/LocalAgent/collected_data/42.data}] message = null cause = com.aveksa.common.ConnectException: Invalid Credentials]
com.aveksa.common.ConnectException: Invalid Credentials
	at com.aveksa.collector.federatedsalesforce.FederatedSalesforceCollectorDriver.testConnection(FederatedSalesforceCollectorDriver.java:142)
	at com.aveksa.collector.federatedsalesforce.adc.FederatedSalesforceAccountDataReader.testConnection(FederatedSalesforceAccountDataReader.java:50)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectData(AccountDataCollector.java:351)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collect(AccountDataCollector.java:302)
	at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectTestData(AccountDataCollector.java:277)
	at com.aveksa.client.datacollector.framework.DataCollectorManager.collect(DataCollectorManager.java:533)
	at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:204)
	at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:102)
	at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:60)
	at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67)
	at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:377)
	at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:364)
	at com.aveksa.client.component.communication.ChangeListHandler.access$300(ChangeListHandler.java:58)
	at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:275)
	at java.lang.Thread.run(Thread.java:748)
...

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment, if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)

Cause

This is a known issue reported in engineering ticket ACM-90781.
 

Resolution

This issue is resolved in the following RSA Identity Governance & Lifecycle patch levels: 

• RSA Identity Governance & Lifecycle 7.1.1 P08
• RSA Identity Governance & Lifecycle 7.2.0 P02