Highlighted
Absent Member.
Absent Member.
649 views

Unable to integrate SQL server with windows authentication mode

Hello,

I am integrating SQL server 2005 with windows authentication on connector appliance, i am getting below error

Connector table parameters did not pass the verification with error [0:Unable to open a connection to [jdbc:sqlserver://xx.xx.xx:1433;DatabaseName=ABCD;Trusted_Connection=True; identity impersonate= True]. (Login failed for user 'siem'. The user is not associated with a trusted SQL Server connection. ClientConnectionId:193defc5-bdaa-4280-8603-2dfde898101f) ] for connector [//location/Localhost/Container 4/MSSQL]. Do you still want to continue?

User is a domain account and SQL server is in the same domain.

Has anyone encounter this error before.

Labels (2)
0 Likes
Reply
4 Replies
Highlighted
Trusted Contributor.
Trusted Contributor.

Hi,

the M$ jdbc driver does not support windows integrated authentication on unix. Either use an SQL Server account or try your luck with jtds (which is not supported but can do windows integrated auth). There's some coverage in here on how to hack jtds to run.

Joachim

0 Likes
Reply
Highlighted
Absent Member.
Absent Member.

Hi Joachim,

I did not get you, see the SQL server 2005 is running on windows system so you mean CA jdbc driver does not support windows authentication on SQL server. Do you have any document/guide for the same.

0 Likes
Reply
Highlighted
Trusted Contributor.
Trusted Contributor.

Hi,

on the ConnApp you can use a variety of jdbc drivers as per connector config guide for the connector in question. The Arcsight supported way to connect to an MS SQL DB is via the M$ jdbc driver for SQL Server. This does support windows integrated authentication on windows only.

See http://msdn.microsoft.com/en-us/library/ms378428.aspx

Some people have hacked together solutions using the open-source jtds driver which is not supported by Arcsight but depending on the connector this needs quite ugly hacks. Search in the forum for jtds to find some info.

As of the latest release of the M$ jdbc driver there seems to be a way of using Kerberos Auth all platforms which I haven't tested yet. Although this needs a working MIT kerberos on the *nix box and on the locked-down connapp you'll have to beg for root access to do the configuration (MIT kerberos seems to be installed).

Using Kerberos Integrated Authentication to Connect to SQL Server

If this works it would certainly be the best way to do this... So if you find a way to make this work, let us know.

Joachim

0 Likes
Reply
Highlighted
Super Contributor.
Super Contributor.

Hi Hemant,

Were you able to fix this issue?

Regards,

Sunil

0 Likes
Reply
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.