All Apps and Add-ons

Authentication Error while Integrating DB Connect 2.x with MS SQL Server 2012 R2 using Windows authentication

richdaleresiden
Explorer

We see following error message on DB Connect 2.0.4 using Java 8 screen while trying to connect to MS SQL Server 2012 R2 using windows user authentication.

com.microsoft.sqlserver.jdbc.SQLServerException:com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user '<windows Domain>\HWQ1156$'. ClientConnectionId:f3db99fb-976d-4477-ba05-80b98e5995fa

It seems as if it is unable to get the value for a variable "HWQ1156$" which would be the user with which we are logged on to the Splunk Server. Do we have to pass this value explicitly somewhere on the configuration file as we do not see it documented or asked anywhere within Splunk or DB Connect Documentation?

1 Solution

richdaleresiden
Explorer

Realized that we missed following few critical steps required for Windows Authentication which are as follows

  1. From the Windows Control Panel, go to Services, and then get properties on "Splunkd Service."
  2. Click the Log On tab, and then change the "Log on as" setting from the Local System account to that of the logged on domain user. Note: The domain user should have sufficient privileges to access the SQL Server instance.
  3. Save your changes, and then restart the Splunk Enterprise server for the changes to take effect.

After the steps are performed on Splunkd Service for the user we are able to connect to MS SQL Server using a windows authentication user on DB Connect 2.0.4.

View solution in original post

richdaleresiden
Explorer

Realized that we missed following few critical steps required for Windows Authentication which are as follows

  1. From the Windows Control Panel, go to Services, and then get properties on "Splunkd Service."
  2. Click the Log On tab, and then change the "Log on as" setting from the Local System account to that of the logged on domain user. Note: The domain user should have sufficient privileges to access the SQL Server instance.
  3. Save your changes, and then restart the Splunk Enterprise server for the changes to take effect.

After the steps are performed on Splunkd Service for the user we are able to connect to MS SQL Server using a windows authentication user on DB Connect 2.0.4.

richdaleresiden
Explorer

Following section has all the required steps under Title "Can't use Windows authentication for Microsoft SQL Server with Microsoft JDBC Driver for SQL Server"
http://docs.splunk.com/Documentation/DBX/2.0.4/DeployDBX/Troubleshooting

0 Karma

richdaleresiden
Explorer

Can we do this connectivity only if Splunk logon is configured using windows authentication? As our Splunk user logins are local ones. Only while connecting to MS SQL Server from DB Connect we plan to use the windows authentication.

0 Karma

chio37
New Member

this doesn't work

0 Karma

chio37
New Member

Can someone help me with this error?
"this driver is not configured for integrated authentication"

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...