A Collibra DQ customer asked us: “Why are Big Query connections not working until we provide Admin authentication?” This leads to a deeper question around security and DQ Connectors:

Q: How can I enforce security for a Collibra DQ Connector, so that only certain roles can read using that connector?
A: Working with Lexanne Painter, we arrived at this process which resolved this for the customer:

Navigate to Collibra DQ > Admin Console > Security Settings > and look at the value of this checkbox:
DB Connection Security
If the DB Connection Security is checked, then it is working with Role Based Access when allowing (or disallowing) users from reading through a DQ Connector.
Lexanne explained the results of this checkbox:
As an example: UserA has the roles Role_Admin & Role_User and UserB only has Role_User …
In the DB connection, Connection1 has Role_User & Role_Admin associated to it and Connection2 only has Role_Admin associated with it. Then UserA would be able to see Connection1 & Connection2 … UserB would only be able to see Connection1 because they do not have Role_Admin associated to their user to be able to see Connection2."
Navigate to Collibra DQ > Admin Console >DB Access tile, and look at what it says there:

5: You should see a dialogue of the Connection Names and the Roles which can access them. This will be enforced when the DB Connection Security is checked (in step 2. above).

For example, if there are no Roles associated with the Connection Name then the security is enforced by Role Based Access:

When the customer added a role to that Connection Management dialogue, it worked!