topic Restricting access to a report in QlikView

Restricting access to a report

Wed, 20 May 2015 09:58:21 GMT

I have a report that I have used Section Access and a spreadsheet with usernames and passwords to restrict access. This part of the process works fine in that you need to enter a username and password to open the report in the web browser or the client application. My issue lies in the QMC when my reloads take place. All my reports reload apart from the one that has the security restrictions using Section Access. I have made sure my admin username and password is on the spreadsheet but that still does not make it work. Is there something I have missed?

I have attached a copy of the log file as best I could as I cannot seem to be able to just copy and paste the whole log file.

Thanks

Steve

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 10:00:10 GMT

Hi Steve,

have you added the Qlikview Service account into Section Access as ADMIN?

Andy

Re: Restricting access to a report

Wed, 20 May 2015 10:11:10 GMT

Hi Andy

I haven't no as I didn't even know I had a qvservice user setup. I have just asked the company that setup Qlikview for us what the password is. Will let you know if that fixes it.

Thanks Steve

Re: Restricting access to a report

Wed, 20 May 2015 11:55:16 GMT

Hi Andy

Added the qvservice user to my spreadsheet with the usernames and passwords. Still fails with the same errors as far as I can see from the log file.

Thanks Steve

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 12:01:53 GMT

HI Steve,

you'll need to reload it from QV Desktop and save it before running it from QMC

Andy

Re: Restricting access to a report

Wed, 20 May 2015 12:08:04 GMT

Hi Andy

Did that. Amended spreadsheet, saved, reloaded and saved the qvw file, then waited for it to reload in the QMC. Then it failed.

Thanks Steve.

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 12:17:28 GMT

Hi Steve,

did you put the Service account name in UPPER CASE etc.

Andy

Re: Restricting access to a report

Wed, 20 May 2015 12:20:22 GMT

Hi Andy

service account name is lowercase on my server. Should that make a difference?

Thanks Steve

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 12:56:10 GMT

Nope, but it has to UPPER in Section Access

Andy

Re: Restricting access to a report

Peter_Cammaert — Wed, 20 May 2015 13:02:53 GMT

In your Excel, the service account should have ACCESS=ADMIN and an empty Link field. The latter only in case you are using data reduction.

Actually, the best thing you can do is hardcode the service account in an INLINE table in SA, and then add all Excel rows with a CONCATENATE LOAD to that table. This will make sure that once operational, the server reload will never fail on you again.

Peter

Re: Restricting access to a report

Wed, 20 May 2015 13:22:24 GMT

I have tried various different options within my spreadsheet but it is still failing to reload. Like I said the security works on the document just not on the reload.

example spreadsheet below:

Thanks Steve

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 13:30:23 GMT

What's in the section access part of your script?

Andy

Re: Restricting access to a report

Peter_Cammaert — Wed, 20 May 2015 13:30:58 GMT

Ah, now we got something.

Drop the password field, and rename USERID into NTNAME. That should do the trick.

Peter

Re: Restricting access to a report

Peter_Cammaert — Wed, 20 May 2015 13:35:24 GMT

Or if you hold on to the non-SingleSignOn way of granting access (we're all Windows users, so Windows already knows who we are - you seem to supply a domain name for all UserIDs), enter the credentials of one of the admin accounts in the section access fields at the bottom of the Reload tab in QMC (No Publisher) or in the Data Protection area of the Task Reload tab (if you've got a Publisher)

Best,

Peter

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 13:38:34 GMT

Agree with the above, USERID is not the same as the USERNAME, using NTNAME instead with all of them in upper case, will mean your logon credentials will be used to access the qvw rather than having to enter a user name and password etc.

Andy

Re: Restricting access to a report

Peter_Cammaert — Wed, 20 May 2015 13:45:56 GMT

And a little explanation: USERID and PASSWORD fields make the server always produce a login page where you can enter the correct credentials. The reload engine however is nothing more than a stripped QV Desktop without a user interface: a black box without arms or legs. The reload engine has no means whatsoever to ask you for a username or a password. However, QlikView server can pass these credentials as parameters to the engine during startup, on condition that you supply the correct values in those QMC fields.

I still think the NTNAME approach will suit you better.

Best,

Peter

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 13:47:14 GMT

Hi Steve, if you do want to do it the original way, you can enter one of the already created user details here on the reload tab of your document 🙂

Andy

Re: Restricting access to a report

Wed, 20 May 2015 15:40:55 GMT

Hi Both

I tried as you have said. My spreadsheet now looks like this:

And the reload page for the report on QMC looks like this:

I tried it with TSL\ in front of the username but that failed too. Should I be using the QVSERVICE username for this? The ATLAS login has admin rights as this is the login that the QMC was installed under.

Thanks Steve

Re: Restricting access to a report

awhitfield — Wed, 20 May 2015 15:54:06 GMT

You don't need that bit if you have changed it to NTNAME, just reload manually etc then try the QMC. Just a thought, is the QVSERVICE account actually a domain account OR a local server account? If it's local you don't need the TSL prefix

Andy

Re: Restricting access to a report

Peter_Cammaert — Thu, 21 May 2015 07:23:08 GMT

Maybe it's time to start over again. You do have an original version of your document without Section Access, don't you? Make a copy of that original (call it "... - SECURED.qvw" or something), add or enable SA in your script, reload in the desktop with the most recent version of the Excel and store in the server document root. Then let the server perform a reload on its own.

IMHO the SA data in the current document may have been messed up too much already...

Best,

Peter