Salesforce Account Data Collector in RSA Identity Governance and Lifecycle will fail when configured using the application wizard
3 years ago
Originally Published: 2018-05-01
Article Number
000041726
Applies To
RSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: All
 
Issue
After configuring Salesforce using the application wizard under Resources tab, Applications, Create Application, the created Salesforce ADC fails test collection 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: Login request failed with status code: 500 
Caused By Stack com.aveksa.common.ConnectException: Invalid Credentials at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:143) at com.aveksa.collector.salesforce.adc.SalesforceAccountDataReader.testConnection(SalesforceAccountDataReader.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)
Caused by: com.aveksa.common.DataReadException: Login request failed with status code: 500 
	at com.aveksa.collector.salesforce.SalesforceCollectorDriver.getSession(SalesforceCollectorDriver.java:207) 
	at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:140)
	 ... 14 more End Stack
Cause
When the application wizard is run, the Salesforce OAuth token is configured for the AFX connector but not copied to the Salesforce account data collector.
Resolution
To resolve this issue, you must request a new OAuth token within Salesforce and manually update it in both the AFX connector and the account data collector. Requesting the token will invalidate the existing OAuth token which is why it must also be replaced in the previously working AFX connector.

 

To update the AFX connector

  1. Go to the AFX menu, Connectors.
  2. Click on the connector name, then Edit.
  3. Go to the Settings tab and update the Client Secret field with your new OAuth token.

To update the account data collector

  1. Go to Collectors menu, Account Collectors.
  2. Click on the collector name, then Edit.
  3. Click Next and update the Security Token field with your new OAuth token.

Related Articles

Trending Articles

Don't see what you're looking for?