Salesforce Collector is throwing 'Invalid Credentials' error after patching to RSA Governance & Lifecycle 8.0.0 P06
Originally Published: 2025-04-30
Article Number
Applies To
- RSA Governance & Lifecycle 8.0.0 P06
Issue
Following the upgrade to RSA Governance & Lifecycle 8.0.0 P06, the Salesforce collector is failing with 'Invalid Credentials' (HTTP Status Code 400)
The following error is logged to the aveksaServer.log file.
03/26/2025 09:52:06.751 ERROR (ApplyChangesChangeDataRequest-1742910008815-1742910008815) [com.aveksa.collector.salesforce.SalesforceCollectorDriver] Invalid Credentials
com.aveksa.common.DataReadException: Response with HTTP Status Code 400
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.processResponse(SalesforceCollectorDriver.java:293) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.get(SalesforceCollectorDriver.java:279) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.isVersionSupported(SalesforceCollectorDriver.java:227) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:136) ~[classes/:?]
at com.aveksa.collector.salesforce.adc.SalesforceAccountDataReader.testConnection(SalesforceAccountDataReader.java:50) ~[classes/:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectData(AccountDataCollector.java:343) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collect(AccountDataCollector.java:295) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectTestData(AccountDataCollector.java:270) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.framework.DataCollectorManager.collect(DataCollectorManager.java:585) ~[datacollectorframework.jar:?]
at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:207) ~[components.jar:?]
at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:105) ~[components.jar:?]
at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:70) ~[components.jar:?]
at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67) ~[datacollectorframework.jar:?]
at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:378) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:366) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler.access$100(ChangeListHandler.java:48) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:278) ~[components.jar:?]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_442]
03/26/2025 09:52:06.754 ERROR (ApplyChangesChangeDataRequest-1742910008815-1742910008815) [com.aveksa.client.datacollector.framework.DataCollectorManager] DCM281: Collection Failed: CollectionFailedEvent[cmi = CollectionMetaInfo[{ID=12, run_id=1742910008815, collector_id=83, test-run=true, collector_name=GEM-ADC, data_size=0, data_file=/home/oracle/wildfly-24.0.1.Final/domain/servers/img-server-1/tmp/vfs/deployment/deployment4dbfe2a90d6b8b63/aveksa.war-3b8159ad15a53e2f/WEB-INF/LocalAgent/collected_data/12.data}] message = null cause = com.aveksa.common.ConnectException: Invalid Credentials]
com.aveksa.common.ConnectException: Invalid Credentials
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:142) ~[classes/:?]
at com.aveksa.collector.salesforce.adc.SalesforceAccountDataReader.testConnection(SalesforceAccountDataReader.java:50) ~[classes/:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectData(AccountDataCollector.java:343) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collect(AccountDataCollector.java:295) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.collectTestData(AccountDataCollector.java:270) ~[datacollectors.jar:?]
at com.aveksa.client.datacollector.framework.DataCollectorManager.collect(DataCollectorManager.java:585) ~[datacollectorframework.jar:?]
at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:207) ~[components.jar:?]
at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:105) ~[components.jar:?]
at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:70) ~[components.jar:?]
at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67) ~[datacollectorframework.jar:?]
at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:378) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:366) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler.access$100(ChangeListHandler.java:48) ~[components.jar:?]
at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:278) ~[components.jar:?]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_442]
Caused by: com.aveksa.common.DataReadException: Response with HTTP Status Code 400
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.processResponse(SalesforceCollectorDriver.java:293) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.get(SalesforceCollectorDriver.java:279) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.isVersionSupported(SalesforceCollectorDriver.java:227) ~[classes/:?]
at com.aveksa.collector.salesforce.SalesforceCollectorDriver.testConnection(SalesforceCollectorDriver.java:136) ~[classes/:?]
... 14 more Cause
The problem occurs because the SOAP request header sent to Salesforce has two 'Authorization' fields, each containing an empty token.
This causes the Salesforce endpoint to fail the request.
Resolution
This issue is resolved in the following version/patch:
- RSA Governance & Lifecycle 8.0.0 P06_HF01
- RSA Governance & Lifecycle 8.0.0 P07_HF01
Related Articles
Getting an "Unable_To_Migrate_Connectors_Or_Templates" error after patching to 8.0.0 P05 in RSA Governance & Lifecycle Number of Views After patching to RSA Identity Governance & Lifecycle 7.0.2 P03+, emails are not generated and sent due to the error 'Ille… Number of Views Modification of the LDAP identity source failed with an Error "Unexpected error during command com.rsa.admin.UpdateIdentit… Number of Views Error : Unsupported OS to patch OS Patching is only available on SLES appliances when patching RSA Via Lifecycle & Governance Number of Views Quick Setup Guide - Cloud Access Service POC - Step 1: Plan Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
