RSA Identity Governance & Lifecycle collector throws "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" error
Originally Published: 2018-02-12
Last Modified: 2023-11-30
Article Number
Applies To
RSA Product/Service Type: Data Collection
RSA Version/Condition: 7.0.x
Issue
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
In the aveksaServer.log the message is shown:
02/05/2018 04:48:23.134 ERROR (ApplyChangesRegularThread-6407) [com.aveksa.collector.db.util.DBPerformQuery] GetSchemas
java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)
at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:649)
at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:371)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:215)
at com.aveksa.collector.accountdata.DBGenericAccountReader.getConnection(DBGenericAccountReader.java:874)
at com.aveksa.collector.db.util.DBPerformQuery.getSchemas(DBPerformQuery.java:120)
at com.aveksa.collector.db.util.DBPerformQuery.performQuery(DBPerformQuery.java:74)
at com.aveksa.collector.accountdata.DBGenericAccountReader.performQuery(DBGenericAccountReader.java:921)
at com.aveksa.client.datacollector.collectors.accountdatacollectors.AccountDataCollector.performQuery(AccountDataCollector.java:474)
at com.aveksa.client.datacollector.framework.DataCollectorManager.performQuery(DataCollectorManager.java:579)
at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:492)
at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:120)
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:745)Cause
Resolution
Notes
This is a legacy Knowledge Base Article and only applies to the listed versions which are no longer actively supported.
RSA does not recommend the continued use of the public domain JTDS driver on current versions of the product. RSA recommends customers use the JDBC driver specific for their database.
Related Articles
Authentication method failed error when LDAP user tries to login to RSA Authentication Manager 8.x consoles 110Number of Views Cannot get RSA Federated Identity Manager (FIM) to start as Microsoft Windows service 11Number of Views RSA Authentication Agent 7.2.1 for Windows cannot determine challenge group if the user submits fully qualified domain nam… 224Number of Views Users cannot authenticate with login name in domain\sAMAccountName format using MFA Agent 2.0.1 96Number of Views RSA SecurID Software Token Converter 3.1 Release Notes 41Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?