Windows Authentication: Microsoft SQL Server

[nadhikari_identitynow (Nischal Adhikari)]

Hello Experts,

I am trying to connect ISC with MS SQL server using the out-of-the box connector available in SailPoint ISC. We are trying to use Windows Authentication.

We have followed some of the guidance provided here in the community:

MSSQL direct connection windows integrated

Attempting to establish an MSSQL direct connection with windows authentication and there are lots of points referencing SQLJDBCdriver.config and krb5.config but all of them seem to assume a level of familiarity with these files and their structure that I do not have. Are there any kind of examples that someone could point me to on either how to write these or examples that have dummy configuration in them?

ISC/MSSQL/Kerberos integration [unable to obtain principal name for authentication]

Hello All, Recently i’m working on itegration between ISC and MSSQL on-prem database. Our customer request us to use Windows Authentication so additional step is to authenticate to Kerberos service. However i’m receivig follwowing error: Error Received: > [ ConnectorException ] [ Error details ] The server encountered an unexpected error while contacting target system. Please check the logs. Kerberos Login failed: Integrated authentication failed. ClientConnectionId:92149d5e-2afb-4b3e-a324-92…

The issue we are having is we are getting the “unable to obtain Principal Name …”.

The second link I have included here has very nice and step by step guide document from Brennen Scott that we were trying to follow: However,
We won’t be able to use the same service account that runs the MSSQLSvc and have the right SPN record as shown in the document.

We need to use a different windows account but we cannot set the SPN that it needs since it is used by the service account that runs the MSSQLSvc service in the server.

So, we are not able to move forward and hoping if anyone here faced the similar issue and had some insights on resolution. Any information helps.

Thanks in advance.

Thanks,
Nischal

[Shubhams_009 (Shubham Shende)]

Hi @nadhikari_identitynow,

In the past for OOTB connector (Microsoft SQL Server) we had the same requirments to use Windows account for AuthN so we used JTDS driver instead of JDBC and used below configs.

Auth Type: Windows AuthN
DB URL: jdbc:jtds:sqlserver://:;domain=<your_domain>integratedSecurity=true;useNTLMv2=true;
Driver class: net.sourceforge.jtds.jdbc.Driver
Jar file: jtds-1.3.1.jar (can be downloaded from jTDS - SQL Server and Sybase JDBC driver - Browse /jtds at SourceForge.net)

Might worth a try to see what it pulls.

Thanks,
Shubham

[nadhikari_identitynow (Nischal Adhikari)]

Hi Shubham,

Thank you for your response. Just to confirm, you are using generic JDBC connector and JTDS driver? Or you are using Microsoft SQL Server connector and JDTS Driver?
Please confirm.

Thank you.

-Nischal

[Shubhams_009 (Shubham Shende)]

We are using Microsoft SQL Server connector and JTDS Driver.

Thanks,
Shubham

[sk8er23 (Anthony Huxtable-Jones)]

Did you ever resolve this?

[nadhikari_identitynow (Nischal Adhikari)]

No. We weren’t approved to use the open-source JTDs. SQL Authentication was eventually used.