Support for Windows Authentication _without_ a domain

[chucker]

• SQL Operations Studio Version: 0.27.0-insider

SQL Server Management Studio supports connection to a Windows server without the need for a domain on that end, as long as it has a matching username and password.

SQL Operations Studio, however, lists an AD domain as a prerequisite:

Access to a Windows domain-joined machine in order to query your Kerberos Domain Controller.

Presumably, SSMS achieves this through a different protocol (perhaps NTLM?), since there's apparently no actual Kerberos server on the other end in such a setup.

[kburtram]

@chucker are you referring SQL Login authentication where SQL Server managed the Users and Logins? Or are you referring to local Windows user accounts?

[chucker]

No, I'm referring to Windows user accounts.

Specifically, we have a local AD, but several servers outside that domain.

If i have an AD user MyCorp\chucker with credentials 123, and a remote server with a server-local user MyWindowsServer\chucker with identical credentials 123, I can use SQL Server Management Studio integrated authentication, even though MyWindowsServer has no ability to query MyCorp's AD.

[steelwil]

If I VPN to work I am unable to use windows authentication to connect to our databases, because my machine is not on the domain. I have to use the runas command which is cumbersome, and on Linux I do not have the runas command! If there is a work around please let me know.

[ObsidianPhoenix]

This is probably related to #112

[kburtram]

@aaomidi do you know if the auth changes we're planning in SqlClient would address this issue?

[aaomidi]

Hmm, I'm not entirely sure. But potentially yes.

I'll have to understand the scenario completely to be able to answer.

[chucker]

(This scenario is indeed moot if we get #112 instead, which SSMS cannot do.)

[cheenamalhotra]

@chucker Are you looking through documentation only or you have an actual failing scenario that does not work as SSMS?

If i have an AD user MyCorp\chucker with credentials 123, and a remote server with a server-local user MyWindowsServer\chucker with identical credentials 123, I can use SQL Server Management Studio integrated authentication, even though MyWindowsServer has no ability to query MyCorp's AD.

Based on my understanding, this scenario should work just fine same as SSMS. You should not be blocked by any scenario for Windows non-domain accounts when using "Integrated" authentication on Windows.

[cheenamalhotra]

Closing this issue due to inactivity.