How to avoid that the technical user account has access to all the data?

[kbiesemans]

This week I heard an interesting question at one of our customers. They were afraid to use the Publisher to extract data and save it into QVDs. The reason is that the Publisher got executed by a technical user account which will get access to all the extracted data, so all the data of that company. A technical user account is not linked to a physical person. So if someone can find the password of that technical user account, they gain access to all the sensitive data. And you can't make someone responsible for losing the password.

What they would like to acheive is that one user is responsible for one domain, e.g. HR, Marketing, Finance,... Does someone see a solution for this?

[ashfaq_haseeb]

HI,

You can Schedule Task via QlikView server and if required give remote access to QEMC.

Regards

ASHFAQ

[senarath]

Hi,

what about limit the folder access user wise.This would be the windows user either domain or local.

Thanx

[#4]

The issue is that to load the Data the User need the Access Rights. If you want to ensure nobod can use this account the best is to use a non interactive Service User.

[senarath]

What if the case if we put QVD makers into a folder and block other folders.

Further, if the version is publisher, we could use QMC to run scripts as well in which case only remote log on to QMC would do the job.

[Bill_Britt]

Hi,

The attached document should help and give you an understanding of ways to lock down QVS and publisher. It is a little old, but the fundamentals are the same.