on 2016 Aug 10 6:06 PM
I have an SQLA 16.0.1324 database running on a Linux server.
Users connect via an application installed on their Windows desktops and those desktops are part of a Windows Domain.
I tried setting up Integrated Logins and specified the following option to specifically identify the domain controller:
SET OPTION PUBLIC.integrated_server_name = '\\\\DCServer';
When attempting an integrated login I get an error message -130 regarding UserID '' (seems to think the UserID was passed as an empty string).
Checking the ConnectFailed event parameters though, it shows the correct username in appdata as OSUSER=SigerMatt.
Is it possible to use Integrated Login against a Windows Active Directory if the database server is running on Linux?
Any help or advice would be appreciated.
Request clarification before answering.
Windows Integrated Logins is a feature of the Windows OS and requires both the clients and the server to be running on a Microsoft Windows OS. Having the OSUSER alone is not sufficient to make the verification work; some Windows OS-specific functions need to be available to the server.
That is the reason your Linux database server is expecting a UID and a PWD will be supplied.
There are other authentication mechanisms that may be of interest. Those include LDAP and KERBEROS but both are different from Windows Integrated Logins and may not be available in your environment or may not be what you are looking for. Version 17 also introduces support for the Unix/Linux-only PAMUA if that is of any interest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
47 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.