Federated Salesforce Account Collector fails with 'Invalid Credentials' in RSA Identity Governance & Lifecycle
Originally Published: 2020-06-23
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
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:
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
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P08
- RSA Identity Governance & Lifecycle 7.2.0 P02
Related Articles
RSA Identity Governance and Lifecycle invalid credentials for default email account error in when using valid username and… Number of Views Error "Key negotiation exchange failed. Server response was CANCELLED" with RSA Authentication Agent API 8.5 and later Number of Views The server encountered an unexpected condition which prevented it from fulfilling the request when logging out of Self-Ser… Number of Views Getting authentication cookie Number of Views RSA Authentication Client 3.6 Getting Started Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
