Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Learn how to migrate to Qlik Cloud Analytics™: On-Demand Briefing!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Security

Hi all,

I am trying to secure a QVW file, we don't have the server version and some users will be allowed access to the file which I would like to restrict.

Sample Code below

Section Access;

LOAD * INLINE [ACCESS, USERID, PASSWORD, DEPT

ADMIN, Alan, Alan, FINANCE

ADMIN, Sandeep, Sandeep, FINANCE

USER, Nigel, Nigel, FINANCE

USER, Loretta, Loretta, COVERAGE];

Section Application;

star is *;

LOAD * INLINE [DEPT, LOCATIONEX

FINANCE, *

COVERAGE, London

COVERAGE, Dundee

COVERAGE, Glasgow;

On the document opening tab I checked the "Initial Data reduction based on section access"

When I look in the table viewer I can only see the second table but can't see the first although I am asked for a password when I log in and this works as far as Admin rights and User rights are concerned.

Can anyone guide me in the right direction as I seem to be missing something. There is a filed LOCATIONEX in the main data. Hope this makes sense.

Regards

Alan

1 Solution

Accepted Solutions
Not applicable
Author

I would advise to uncheck strict exclusion, because if you don't Qlikview will remove all data that are not in teir securiy range when reloading.

If your users don't see any data, are you sure there are data for COVERAGE group ?

(stupid question, but...)

View solution in original post

9 Replies
prieper
Master II
Master II

The tables used betw statements Section Access ..... Section Application are not visible and not adressable.

HTH
Peter

Not applicable
Author

First of all, this is normal you cannot see the first table because Section access tables are not wiewable.

It seems that your code is correct, If I understant members of COVERAGE can only see London, Dundee and Glasgow locations.

Rgds

Not applicable
Author

Hi Peter,

Thanks for the reply. That explains why I can see the second table in the table viewer. I have now changed the code to:

Section Access;

LOAD * INLINE [ACCESS, USERID, PASSWORD, DEPT

ADMIN, Alan, Alan, FINANCE

ADMIN, Sandeep, Sandeep, FINANCE

USER, Nigel, Nigel, FINANCE

USER, Loretta, Loretta, COVERAGE];

star is *;

LOAD * INLINE [DEPT, LOCATIONEX

FINANCE, *

COVERAGE, London

COVERAGE, Dundee

COVERAGE, Glasgow;

Section Application;

Now I cant see any of the tables created. So far so good but the restrictions still dont work. The user could not open the QVW at first until I unchecked the "Strict exclusion". Does anyone know if there is a sample qvw that I can download that has examples of security already implemented.

Regards

Alan



Not applicable
Author

Hi Spastor,

Thanks for the reply. Crossed posts, I changed the code based on Peters answer but can change back again.

....so if the code is correct the restrictions i.e Coverage can only see London, Glasgow and Dundee should work. At the moment they don't so I am not sure whats the problem is...the help file is not very helpful :-(.

Is there other options which I need to select in document properties for this to work?

Regards

Alan

Not applicable
Author

I would advise to uncheck strict exclusion, because if you don't Qlikview will remove all data that are not in teir securiy range when reloading.

If your users don't see any data, are you sure there are data for COVERAGE group ?

(stupid question, but...)

Not applicable
Author

Hi Spastor,

Your assumption is correct I only want any member of COVERAGE to be able to view LOCATIONEX value either London, Glasgow or Dundee. Any FINANCE member can view all.

Alan

Not applicable
Author

Thanks Spastor. It all works now...fantastic.

Thanks all for your help.

Alan

prieper
Master II
Master II

Except semantic things can't see, why this code should not work. Semantic means that there must be a Field existing, which is called LOCATIONEX and there must be some contents like London, Dundee etc. Please observe correct spelling and Upper/Lower case.

Peter

Not applicable
Author

Thanks for your help Peter, Its all working now. I just needed to uncheck strict exclusion.

Thanks everyone for your help.

Alan