Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Community,
we have a QVW with section access in the hidden script in order to restrict the data in the document.
The section access works for a couple of years now.
Yesterday I activated the publisher license and created a new task to reload and distribute this document once a day.
But after publishing the document section access doesn't work. Each user has access to all data.
Couriously, if I open the published document and do a partial reload the section access works again.
All services run as local Administrator and the Admin is member of QlikView Administrators.
Is there an option I didn't check?
Any ideas?
Thanks in advance
Björn
Hi Björn,
some ideas:
it depends on the type of security you were (are) using within section access.
if it is based on USERID/PASSWD:
you should edit the task and check "Section access" and put the "reload-user" credentials in
if it based on NTSecurity
add the service-user as ADMIN into the section access
HtH
Roland
Hi Björn,
some ideas:
it depends on the type of security you were (are) using within section access.
if it is based on USERID/PASSWD:
you should edit the task and check "Section access" and put the "reload-user" credentials in
if it based on NTSecurity
add the service-user as ADMIN into the section access
HtH
Roland
Hello Roland,
thank you for your answer.
I use a combination of USERID/PASSWD and NTSecurity.
I also have checked "section access" and put the credentials of an ADMIN-User in.
In the logfile I can see, that the section access part is loaded:
07.08.2013 16:26:15: | 5 fields found: ACCESS, USERID, PASSWORD, NTNAME, ROLLE, 1 lines fetched | |
07.08.2013 16:26:15: | 5 fields found: ACCESS, USERID, PASSWORD, NTNAME, ROLLE, 149 lines fetched |
But it still takes no effect.
Before using the publisher the same constellation worked perfectly.
The problem exists since the document gets published by Publisher.
Hello Roland,
the problem is solved now.
I already had the service user in the SA, but without the Domain
After changing the User to <Domain>\<Reload User> the SA works again.
So your answer was correct, thank you!
But I still don't understand, why the logfile says that it has loaded the SA correctly ...
Hi Björn,
glad to help you.
Is it a Bug or Feature, who knows?
RR