Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
The value 'USER' in section access 'ACCESS' field is not working in QLIKSENSE 3.0. I am getting 'Access denied error'.
If I use 'ADMIN',then it is working fine.
Thanks,
Vignesh U.
Oh.. You are using domain id with USERID. That doesn't work. You have to probably use NTNAME instead, like:
ACCESS, NTNAME, GROUP
ADMIN,DOMAINNAME\SA_SCHEDULER,*
USER,DOMAINNAME\QLIKSENSE1,GROUP1
USER,DOMAINNAME\QLIKSENSE2,GROUP2
USER,DOMAINNAME\QLIKSENSE,*
];
Could you please share the section access code ..will have a look
Hi Avinash,
Below is the code. (Domain name is our client's one). My login is with 'DOMAINNAME\QLIKSENSE'. Changing to lowercase is also not working.
Section access;
Load * inline [
ACCESS, USERID, GROUP
ADMIN,INTERNAL\SA_SCHEDULER,*
USER,DOMAINNAME\QLIKSENSE,*
];
Section application;
Star is *;
Thanks.
When you use "*" in section access it actually means 'All the values of field that are mentioned in section access field'. In your case you have not mentioned any Group value explicitly. That's why USER access doesn't get any value to allow to access to. Try putting like:
ACCESS, USERID, GROUP
ADMIN,INTERNAL\SA_SCHEDULER,*
USER,DOMAINNAME\QLIKSENSE1,GROUP1
USER,DOMAINNAME\QLIKSENSE2,GROUP2
USER,DOMAINNAME\QLIKSENSE,*
];
Then your users DOMAINNAME\QLIKSENSE will get all mentioned group members i.e - Group1 and Group2.
Hi Tresesco,
Actually some of the users are having some values in 'Group' field. But I did not show those users in the above table.
Thanks,
Vignesh U.
Have you used Upper() to convert both match your section access values and Group field?
No, Upper() is not used. Both table values have been entered in capital letters.
Oh.. You are using domain id with USERID. That doesn't work. You have to probably use NTNAME instead, like:
ACCESS, NTNAME, GROUP
ADMIN,DOMAINNAME\SA_SCHEDULER,*
USER,DOMAINNAME\QLIKSENSE1,GROUP1
USER,DOMAINNAME\QLIKSENSE2,GROUP2
USER,DOMAINNAME\QLIKSENSE,*
];
I am facing same issue with version 2.2.4.
Sometime it works with USER and sometimes I have to change it to ADMIN