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
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
RSA Authentication Agent for Windows shows no login tiles on the login screen 283Number of Views Mapping login name to UPN name in RSA Authentication Manager 8.x 621Number of Views Unable to login to RSA Authentication Manager via SSH after changing operating system password to contain a backslash (\) 340Number of Views Slow login to RSA Authentication Agent for Windows 7.x 406Number of Views Users cannot authenticate with login name in domain\sAMAccountName format using MFA Agent 2.0.1 84Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?