Qlikview ODBC connector package questions

[Mats_E]

Hi I am evaluating Qlikview ODBC connector package for our Qlikview installation. I have a few of questions related to that. Hopefully someone can help out.

1. When i want to connecto SQL server there dont seem to be an option for "integrated security". Is that supported and if so how would i need to configure that?

2. How do i configure Oracle connection to be SSL? There is no option for that in the setup for the connection. I have read that tsnames.ora is not utilized by the odbc connector package and that it support DSN less connections. 

3. Does anyone have experience with encrypted connection strings? I have tested this abit and cannot seem to find an answer to the question "can you create a connection string on your pc to be used on Qlikview server but encrypted there". When i have tested that scenarion the reload fails with below error. NOTE i have a case open on this topic aswell.

 
20221024T142159.884+0200      Error: Connector reply error: Unable to connect to database:
20221024T142159.884+0200          Error message:
20221024T142159.884+0200      Please check the values for Username‚ Password‚ Host and other properties. Description: Client unable to establish connection. Credentials cannot be decrypted. Make sure that you have updated your connection string accordingly after enabling encryption. Check that QlikODBCConnectorPackage Key and IV exist in Windows Credential Manager.

I have basically read all i can find documentation wise for the ODBC Connector package and also googled my heart out but dont seem to find answers.

Regards Mats

[Jay_Brown]

Hello Mats, thanks for posting!

1. The Oracle Connector does not support NTLM authentication in version 4.0. For that reason, the Windows integrated security option is not available.
   1. Source: https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/Oracle...
2. To configure Oracle via SSL you can download the Oracle client and create a System DSN and configure the SSL options.
   
   1. Some Qlik connectors have this option but not Oracle, see the SQL connector documentation, for example.
3. If you end up using a System DSN for the SSL factor the connection string details would not be presented within the load script.

Does that help at all?

Thank you,

Jay

[Mats_E]

Hi Jay

Thx for the input. Much appreciated. Some followup questions (in bold)

. 1. The Oracle Connector does not support NTLM authentication in version 4.0. For that reason, the Windows integrated security option is not available. What about SQL connection? You can choose NTLM for that but is that the same as Integrated Security then? Ie if selected you dont have to specify username and password?

2. To configure Oracle via SSL you can download the Oracle client and create a System DSN and configure the SSL options. Does this mean that you cannot connect securely (SSL) with Qlikview ODBC connector to Oracle then? We are using standalone Oracle driver today (with system DSN:s created on publisher server). So we are forced to keep on using that?

Also did you have any info on how the "encrypt connection strings" with Qlikview ODBC connector works?. Basically my goal is to encrypt the connection strings. But i have these "challenges"

-How can i encrypt connection strings on Qlikview server without having to actually create them on the Qlikview server? Ie if user creates the connection string  on their pc first to be used on Qlikview server (publisher). 

-If above can be solved would it also work in a clustered publisher setup?

Regards

[Jay_Brown]

I'm more versed on Qlik Connectors than QlikView but I can try to answer and hopefully some others can chime in as well.

1. The Oracle Connector does not support NTLM authentication in version 4.0. For that reason, the Windows integrated security option is not available. What about SQL connection? You can choose NTLM for that but is that the same as Integrated Security then? Ie if selected you dont have to specify username and password?

a) I only have one lab with a database server to test, which is being rebuilt at the moment, but from memory I think this is the case, I'll just need to verify and get back with you.

2. To configure Oracle via SSL you can download the Oracle client and create a System DSN and configure the SSL options. Does this mean that you cannot connect securely (SSL) with Qlikview ODBC connector to Oracle then? We are using standalone Oracle driver today (with system DSN:s created on publisher server). So we are forced to keep on using that?

a) Yes, correct, currently the best option for SSL to Oracle is via a system DSN.

Also did you have any info on how the "encrypt connection strings" with Qlikview ODBC connector works?. Basically my goal is to encrypt the connection strings. But i have these "challenges"

a) I'd want some QV folks to chime in here, I'll see if I can engage someone to answer that part.

[Mats_E]

Hi Jay

Thx for your reply. 

I think regarding NTLM its not to be used anymore and integrated security using kerberos is what is recommended. Dont seem that this exist either for the SQL server connection as you can only choose NTLM there.

Regarding Creating local DSN for oracle driver. Just to be sure i understand you. This is using separate oracle client and not via Qlikview ODBC connector at all right? Ie we would then not be able to use the ODBC connectors ability to encrypt the connectionstrings for Oracle.

Regards

[Jay_Brown]

Hi Mats, understood!

Yes, System DSN instead of the ODBCConnectorPackage.  You should be able to use Kerberos with the Oracle ODBC driver, and you can also encrypt that at the system level.  In QlikView of course it would just say the DSN name.

Does that help?

--J

[Mats_E]

Hi Jay

Thx for the clarification.

Can you elaborate more on how you do this "you can also encrypt that at the system level.  In QlikView of course it would just say the DSN name"

Regards Mats

[avkeep01]

Hi @Jay_Brown, 

Since this is the only thread where the encrypted credentials are mentioned I reply here. But my problem is not on the oracle connector but on the Azure connector. I've created a separate thread: Qlikview connect to Azure SQL database - Qlik Community - 2045739