Hi Rich, in this way you are relying on the OS authorization. I suggest you move to Qlik authorization since the security rules enable to do that and more.
In this way you need to disable users to create data connection in QlikSense, create them centrally pointing to your ODBC DNS and allows users o groups to access to the right data connection
Thanks for the tip, however, we want the users to use their own credentials when connecting to certain data sources. Many of these sources already have a security model built in to them. We are creating an ODBC connection on the server without a user name and password and then the end user can enter that when creating the connection.
If I use the Qlik security rules to provide access to that connection the end user would technically be connecting using whatever credentials Qlik used to create the data connection.
Is there a way to create a data connection to an ODBC source but still force the user to enter their and grant access via Qlik but still force the user to enter their credentials?
Unless you are in a special situation where your users make the app for themselves (self service) or in a big data scenario where Qlik access data at runtime, in a standard situation the data refresh is triggered in batch mode and run with the Qlik service credentials. Data are stored in memory and Qlik provide a profiled access using the Section Access.
Hope this help