You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After an upgrade of DBeaver I got the following error message when trying to connect to SQL Server via NTLM Authentication: "Connection to 'xxxx' cannot be established. Reason: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:xxx"
With DBeaver 23.1.5 the connection works.
With DBeaver 23.2.0 the connection does not work anymore. I tried a few newer versions, including also EA 24.0.5. Same error message.
It is not related to the SQL Driver. Same behaviour with different drivers: 9.2 or 11.2.3 or 12.4 I get the same error message or success depending on the version of DBeaver.
If I downgrade to 23.1.5 or an earlier version, then it works.
I tried several versions after 23.2.0 and they all gave the error message.
Client:
Windows 10 Pro (different PCs).
Server:
Windows Server 2019
SQL Server 2017
Error:
Success:
Driver:
Attached full Logs (Asterisks on sensitive data).
When doing a Diff on the Logs I noticed that in the error logs there is the following additional line:
Framework arguments: -eclipse.keyring C:\Users*******\AppData\Roaming\DBeaverData\secure\secure_storage
And this line is missing in the debug error log:
Start Equinox Java Authentication and Authorization Service (JAAS) [org.eclipse.equinox.security 1.3.1000.v20220801-1135]
Added following Driver Properties / User Properties:
Domain: **** (our Domain)
Password: **** (my Password)
User: ${user}
Steps to reproduce
I try to connect to the database. Error: "Connection to 'xxx' cannot be established. Reason: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:xxx"
Additional context
No response
The text was updated successfully, but these errors were encountered:
cppelf
changed the title
SQL Server NTLM Authentication does not work since DBeaver 23.0.2.0 (The login is from an untrusted domain)
SQL Server NTLM Authentication does not work since DBeaver 23.2.0 (The login is from an untrusted domain)
May 17, 2024
Description
After an upgrade of DBeaver I got the following error message when trying to connect to SQL Server via NTLM Authentication:
"Connection to 'xxxx' cannot be established. Reason: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:xxx"
It is not related to the SQL Driver. Same behaviour with different drivers: 9.2 or 11.2.3 or 12.4 I get the same error message or success depending on the version of DBeaver.
If I downgrade to 23.1.5 or an earlier version, then it works.
I tried several versions after 23.2.0 and they all gave the error message.
Client:
Server:
Error:
Success:
Driver:
Attached full Logs (Asterisks on sensitive data).
When doing a Diff on the Logs I noticed that in the error logs there is the following additional line:
Framework arguments: -eclipse.keyring C:\Users*******\AppData\Roaming\DBeaverData\secure\secure_storage
And this line is missing in the debug error log:
Start Equinox Java Authentication and Authorization Service (JAAS) [org.eclipse.equinox.security 1.3.1000.v20220801-1135]
error__.log
success__.log
error__dbeaver-debug.log
success__dbeaver-debug.log
DBeaver Version
24.0.5 (issue since 23.2.0, ok with 23.1.5)
Operating System
Client: Windows 10, Server: Windows Server 2019 + SQL Server 2017
Database and driver
Driver:
Connection Properties:
Host: IP Address
Port: 1433
Authentication: NTLM
Username: ***
Password: ***
Override following Driver Properties:
Added following Driver Properties / User Properties:
Steps to reproduce
I try to connect to the database. Error: "Connection to 'xxx' cannot be established. Reason: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:xxx"
Additional context
No response
The text was updated successfully, but these errors were encountered: