Integrated security from IDM to MS SQL Database

[clotilde_martinez]

Hi IDM experts,

I have to connect IDM to a MS SQL Database, using the equivalent of "Windows authentication".

IDM is installed on a unix server. I think I got the overview of what to do, but i'm stuck. I added integratedsecurity=true to my db connexion string. I get the following error : This driver is not configured for integrated authentication.

Is is quite similar to what Matt had here : https://answers.sap.com/questions/11198836/sqljdbcauthdll-reference-in-a-dispatcher.html

First of all, I downloaded again my jdbc driver from microsoft website. I found the file to rename in the zip and put it in my java jre/bin folder. Is it the right place to put it? I guessed that since this java folder is in my dispatcher properties it should find it. I then restarted my dispatcher but no success.

So two questions : where should i put this sqljdbc_auth.dll and how should i declare it to be found?

Then, I think I'll probably be stuck again : should i also create a different dispatcher, ran by the windows user that should connect to the DB or is it another way to do it? Also, DB string connexions in IDM require a user and a passord, if i put in something wrong, will it be ignored? Or should i go through a script?

Thank you!

Clotilde

[lambert-giese · Accepted solution]

Clotilde, I've never done myself what you're trying to achieve, but Alex' comment regarding the DLL is definitely correct: you can't use this on Linux. So I'm pretty sure putting the DLL into whatever directory won't solve your problem. Microsoft might not even ship any Linux version (ending in .so) of this shared library - at least I didn't found any mention of sqljdbc_auth.so anywhere.

This StackOverflow answer mentions that you need to have a different configuration on the SQL client/JDBC driver side to make integrated security work on Linux by using a different security mechanism (Java/Kerberos). You may want to try that suggestion out.

[clotilde_martinez · Accepted solution]

Hi Lambert,

thank you for your answer. we indeed used kerberos and it seems to work, I'm currently testing it.

Thanks for the tip!

Clotilde

[clotilde_martinez · Accepted solution]

Hello,

after testing, the solution is this one : in the database connexion on /idm/admin, put your databasename followed by :

DBname;integratedsecurity=true;authenticationScheme=NTLM;realm=<user domain>;encrypt=false

I still had to put a user and a password but it is not a local db user so the team is happy.

Cheers,

Clotilde