topic Re: Access in webview in QlikView

Access in webview

limingthefirst — Wed, 25 Nov 2020 16:16:04 GMT

Hi All,

I have an issue with user access in webview.

I can open the qvw in desktop, and I can see the qvw when published in QMC, but it back to login frame in webview when I click the qvw.

Below is user Section, and how should I modify it or configure QMC?

ACCESS	NTNAME	CATEGORY	PRODUCT
USER	USER1	A	a
USER	USER2	B	b
USER	USER3	*	c
ADMIN	ACCESSPOINT	A	*
ADMIN	ACCESSPOINT	B	*
ADMIN	ACCESSPOINT	*	a
ADMIN	ACCESSPOINT	*	b
ADMIN	ACCESSPOINT	*	c

I attached two qvw files:

access.qvw work fine, but it take lot of time and space.

access2.qvw can not be opened in webview.

The NTNAME field format is "ACCOUNT" not "DIRECTORY\ACCOUNT" in my useraccess.xlsx, and working well.

Best Regards

Ming

Re: Access in webview

Miguel_Angel_Baeyens — Tue, 15 May 2018 09:15:58 GMT

Check that the NTNAME matches with the output of OSUser() for any given user.

It usually returns a value in the form "DIRECTORY\ACCOUNT". If so, you need to include the part in bold as well.

Re: Access in webview

limingthefirst — Tue, 15 May 2018 09:29:14 GMT

Thanks your suggestion,

I had attached the qvw, could you help to review the code in script?

The NTNAME field format is "ACCOUNT" not "DIRECTORY\ACCOUNT" in my useraccess.xlsx, and working well in access.qvw.

Re: Access in webview

big_dreams — Tue, 15 May 2018 09:39:39 GMT

Hi,

as miguel suggested when you login on access point then what is outcome of osuser(). You have to use that name in your section access script

If you don't get it.

try below step.

1: create blank qlikview application.

2: use text object > write expression > = osuser()

3: save it.

4: publish it on server.

5: open that application in access point.

6: check what is value coming in that text object.

Regards,

Re: Access in webview

limingthefirst — Tue, 15 May 2018 09:43:04 GMT

Hi Max,

I'll try your steps later, thank you~

Re: Access in webview

Miguel_Angel_Baeyens — Tue, 15 May 2018 09:52:11 GMT

NTNAME must coincide with the output of the OSUser() function, which returns the account name as seen by QlikView when any user logs in. In most cases -if not all, this follows that convention: DIRECTORY\ACCOUNT

DIRECTORY usually refers to the name of the user directory, active directory, SSO, LDAP, etc. as it is specified in the QMC > Director Service Connectors > Directory Label or the domain in the case of Windows.

Re: Access in webview

limingthefirst — Thu, 17 May 2018 07:36:55 GMT

Hi Max,

I've updated to "DIRECTORY\ACCOUNT",but it still go back to login frame.

Re: Access in webview

limingthefirst — Thu, 17 May 2018 07:38:34 GMT

Hi Miguel,

Thanks for your detailed explanation,

but it still go back to login frame while I've updated to "DIRECTORY\ACCOUNT" format.

Re: Access in webview

Miguel_Angel_Baeyens — Thu, 17 May 2018 08:33:27 GMT

Is your authorization in QMC set to NTFS or DMS?

Is the format the same as returned by the function OSUser()?

Are the web servers set to authenticate accordingly NTLM, Header, etc?

Re: Access in webview

limingthefirst — Fri, 18 May 2018 08:40:55 GMT

Hi Miguel,

Is your authorization in QMC set to NTFS or DMS?

DMS

Is the format the same as returned by the function OSUser()?

Yes, Same as OSUser()

Are the web servers set to authenticate accordingly NTLM, Header, etc?

We use custom user.

Re: Access in webview

Miguel_Angel_Baeyens — Fri, 18 May 2018 11:15:48 GMT

If you are using Custom Directory try before using USERID and PASSWORD (or only USERID) and make sure that it works. If it does then move to NTNAME.

Re: Access in webview

limingthefirst — Sun, 20 May 2018 05:25:22 GMT

Hi Miguel,

Thanks for replying this, I dont have login permissions on weekend, so I cant test the way of USERID and PASSWORD,

but maybe it does not work too, because every user have 8 fields, such as PRODUCT,CATEGORY_L2,CATEGORY_L3,BUYER_CODE etc. So should I make an ReductionKey or complex authorization with below topic?

Basics for complex authorization

Re: Access in webview

Miguel_Angel_Baeyens — Tue, 22 May 2018 06:34:21 GMT

Use section access first without any reduction field and verify that it works as expected and that the username, domain, etc. are passing through just fine.

For the reduction fields yes, I would recommend to create a key in the section access which links to another table in the data model and resolves such key. Start with a simple user, one with access to only one of the values in those fields, make sure it works and keep adding more complex users.

Note that what section access does roughly speaking is what you can do in the Desktop using menu File > Reduce Data > Keep Possible Values. So if you add the users table to the script, but without the lines section access / section application, you should be able to select one user and see the required white values for each of the reduction fields this user has assigned.

If you don't, then the reduction table is not working. I would develop this way, instead of enabling section access, until I'm sure all users see what they are expected to see.

Re: Access in webview

limingthefirst — Tue, 22 May 2018 08:01:11 GMT

I get it, thanks for your suggestion, and I will work on it by every steps.