Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello
I have a requirement to secure QVD files from being consumed by a Team of developers
you know developers can create a folder data connection and thus can consume QVD files seemlesly
How can I secure a folder from being accessed by a team of developers via creating a folder data connection?
I know via security rules but none of my trials worked
kindly help
assume no security rules created yet
@Sonja_Bauernfeind
How about not allowing your teams to create connections at all, and instead have them created by an Administrator that can be the gatekeeper?
-Rob
One way having security rule for assigning connections to required developers via AD groups. So, do you have this concept? IF so, I might help having the correct security rule 🙂
But, how about in case if the developers access to File share and copy to their File share and consume it if that is real sensitive?
Hello @Anil_Babu_Samineni
the folder location (network path) is protected from unwanted users/developers via windows security
but as you know creating a folder data connection is done by the user account that runs the qlik sense engine and not the user himself so even if the folder is secured via windows security,unwanted users can still create folder data connection to the restricted folder and so we still need qlik sense security rules
Kindly help
I am not expert in this subject, In our organization not everyone has access to 'Create data connection'. You might think of disabling that button through security rule. You may define new custom property to assign protected folder data connection to few specific users only.
Hello @Digvijay_Singh
We cannot disable the create new connection button
We have several teams
Team1 can create folder connections to any folder or network path
Team2 cannot create data connections to a folder location (sensitive data)
Team3 can only create data connections to one specific folder
How about not allowing your teams to create connections at all, and instead have them created by an Administrator that can be the gatekeeper?
-Rob
This is what we'll go for
After all there is no way to restrict developers from creating a folder data connections to a specific folder location!!