Salesforce Account Data Collector in RSA Identity Governance and Lifecycle will fail when configured using the application wizard
Originally Published: 2018-05-01
Article Number
Applies To
RSA Version/Condition: All
Issue
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
Resolution
To update the AFX connector
- Go to the AFX menu, Connectors.
- Click on the connector name, then Edit.
- Go to the Settings tab and update the Client Secret field with your new OAuth token.
To update the account data collector
- Go to Collectors menu, Account Collectors.
- Click on the collector name, then Edit.
- Click Next and update the Security Token field with your new OAuth token.
Related Articles
Active Directory Account Collector fails with 'Naming Exception happened' in RSA Identity Governance & Lifecycle Number of Views Active Directory Account Data Collectors are failing in pre-processing in RSA Identity Governance & Lifecycle Number of Views VIA L&G What is the meaning of the NONE button in bulk review Number of Views Pagination fails by using base URL in a generic REST salesforce ADC/EDC collector in RSA Governance & Lifecycle Number of Views Partially orphaned accounts occur in RSA Identity Governance & Lifecycle when the ADC defines multiple user resolution att… Number of Views
Trending Articles
How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
