Google Apps Data Collectors and AFX Connectors fails with authentication errors in RSA Identity Governance & Lifecycle
Originally Published: 2017-11-08
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 6.9.1
Issue
com.google.gdata.util.AuthenticationException: Error authenticating (check service name).
Caused by com.google.gdata.util.AuthenticationException: Error authenticating (check service name)
Caused By Stack com.aveksa.common.ConnectException: com.google.gdata.util.AuthenticationException:
Error authenticating (check service name)
at com.aveksa.collector.googleapps.adc.GoogleAppsAccountDataReader.getUserService(GoogleAppsAccountDataReader.java:139)
at com.aveksa.collector.googleapps.adc.GoogleAppsAccountDataReader.testConnection(GoogleAppsAccountDataReader.java:91)
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)
The same errors show in the log files if an attempt is made to run a full collection or use the connector in a request (i.e. not testing.)Caused by com.google.gdata.util.AuthenticationException: Error authenticating (check service name)
Caused By Stack com.aveksa.common.ConnectException: com.google.gdata.util.AuthenticationException:
Error authenticating (check service name)
at com.aveksa.collector.googleapps.adc.GoogleAppsAccountDataReader.getUserService(GoogleAppsAccountDataReader.java:139)
at com.aveksa.collector.googleapps.adc.GoogleAppsAccountDataReader.testConnection(GoogleAppsAccountDataReader.java:91)
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)
Cause
Resolution
Related Articles
AFX Connectors remain in a Deployed state and 'Failed to get flows for server. No associated server id' error in RSA Ident… Number of Views AFX Connectors remain in a Deployed state, mmc-console fails to start and 'Unable to initialize query handler' acccessing … Number of Views Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle Number of Views AFX Connectors remain in a Deployed state and 'Could not locate data file kahadb/db-XXX.log' error in RSA Identity Governa… Number of Views Running AFX Connectors fail, connectors remain in "Not Deployed" state in RSA Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?
