Section Access from QVD

[nicolett_yuri]

Hello,
I'm trying to make an access control through AD. I'm getting the data I need via LDAP.
All this is working, but when trying to add a user through an INLINE, this and only this user can not connect to the application.
Can you help me?


I use two applications, one to generate the QVD and another that reads this file QVD.

Here is the code I generate the QVD:

Access:
LOAD
'Admin' as ACCESS,
'Swbi ' & trim (sAMAccountName) the NTNAME,
telephoneNumber the restriction;
SELECT
sAMAccountName,
telephoneNumber
FROM 'LDAP: / / swbi'
WHERE objectClass = 'user'
and memberOf = 'cn = App01.ADMIN, OU = Groups, OU = SWB, SWB DC =, DC = inf, dc = br ";

LOAD
'USER' the ACCESS
'Swbi ' & trim (sAMAccountName) the NTNAME,
telephoneNumber the restriction;
SELECT
sAMAccountName,
telephoneNumber
FROM 'LDAP: / / swbi'
WHERE objectClass = 'user'
and memberOf = 'cn = App01.USER, OU = Groups, OU = SWB, SWB DC =, DC = inf, dc = br ";

CONCATENATE

Access:
LOAD * INLINE [
ACCESS, NTNAME
ADMIN srvswbbi \ QlikView
];

Now follows the application code that loads the QVD:

Access Section;
LOAD UPPER (ACCESS) the ACCESS
NTNAME,
Restriction
FROM QVD \ SECTIONACCESS \ Acesso.qvd (QVD);

Application Section;

Data:
LOAD * INLINE [
ID, Restriction, QTD_NUM
01, 99999999, 10
02, 23455, 2
03, 22222, 3
04, 886767, 11
05, 99999999, 90
06, 99999999, 88
07, 99999999, 6
08, 9983613, 200
09, 3837661, 30
10, 8872836, 95
];

My problem is that the user SRVSWBBI \ QlikView can not access the application.

[#2]

Hi,

Try put the clausule WHERE 1 = 1

Access Section;
LOAD UPPER (ACCESS) the ACCESS
NTNAME,
Restriction

FROM QVD \ SECTIONACCESS \ Acesso.qvd (QVD)

WHERE 1 = 1;

[nicolett_yuri]

I tried but it does not work.

All users coming from the AD work, just not the user's INLINE

[Anonymous]

Yuri,
I see a couple problems here:
1. Comma is missing after ADMIN in INLINE, so it is one field. Must be:
ADMIN, srvswbbi\QlikView
2. The field name used for data restriction must be uppercase.

[nicolett_yuri]

I found the error.
In the session access QlikView, when we want to make a data reduction. We can not try to restrict some data that does not exist in the cloud data.
In my opinion I do not agree with this because QlikView should have a more specific error, not only request authentication again. Maybe that way it would be easier to identify the error.

That would be a hint for the implementation of QlikView, improve error messages.

[Anonymous]

I find it convenient to trobleshoot Section Access by using "Initial Selection" instead of data reduction. It shows what exactly is going on.