topic Re: Question about Qlik Sense UDC (via SQL ODBC) in Management & Governance

Question about Qlik Sense UDC (via SQL ODBC)

Bo_PT — Fri, 26 Jul 2024 11:54:43 GMT

Hi, there,

I created a UDC (user directory connector) in our Qlik Sense server. UDC type: SQL (via ODBC). In SQL server database, I created a QSUDCUsers table (as user table) and QSUDCAttributes table (as attributes table). See attached image.

It seems working. I reloaded UDC and users showed up in QMC. However, later I realized that I only inserted data into QSUDCUsers table, but forgot to add data into QSUDCAttributes table. The QSUDCAttributes table is still empty. Then why do we need attributes table here?

Re: Question about Qlik Sense UDC (via SQL ODBC)

Levi_Turner — Fri, 26 Jul 2024 13:20:02 GMT

Because the point of a UDC is to bring in attributes. A user record will be created if it does not exist upon successful authentication (this is why you can login and license the software immediately after installation).

Re: Question about Qlik Sense UDC (via SQL ODBC)

Bo_PT — Fri, 26 Jul 2024 15:09:09 GMT

@Levi_Turner Thanks for your reply.

So if we have a user record in QSUDCUsers table but does not have associated record in the QSUDCAttributes table. This user cannot log in Qlik Sense even his name show up in user list. Is that correct?

Re: Question about Qlik Sense UDC (via SQL ODBC)

Levi_Turner — Fri, 26 Jul 2024 15:36:46 GMT

The user can log in if the Identity Provider (via the Virtual Proxy) authenticates them. In a brand new site, this will be Windows authentication. UDCs do not influence authentication, they assist with authorization. UDCs are designed to fetch user attributes, ideally for use in security rules / license rules so that authorization can be allocated dynamically at scale.