Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I’m new to Section Access. Worked with it some over the last couple of days and found it relatively easy to understand using USERID. We’re going to authenticate using NTNAME, which I scripted and it works fine.
However, I need the final version to authenticate based on two levels: 1) SUP 2) CCP //Supervisor and CCP
I read Henric’s posts on Authorization using a Hierarchy: https://community.qlik.com/blogs/qlikviewdesignblog/2013/11/25/hierarchy-authorization and https://community.qlik.com/blogs/qlikviewdesignblog/2013/11/11/unbalanced-n-level-hierarchies.
Both have me really confused.
I have the NTNAME fields – aliased as NETWORKID.
Section Access;
Authorization:
Load
ACCESS,
'INTEGON\'&I_EmpID as NTNAME,
I_EmpID as %NETWORKID;
SQL Select
'USER' as ACCESS,
I_EmpID
From db;
Section Application;
Load
Upper(SupID) as %NETWORKID,
Upper(SupID) as NetworkID;
SQL Select
I_EmpID as SupID,
Name as SupervisorName
From db;
(I have an inline load that concatenates an ADMIN ID to the Authorization table. Didn’t include it above)
Network ID links to the other tables. This scenario works. I just need to configure it to where the Supervisor see’s his/her people and the ccp only see’s his/her data.
Am I going about this wrong? Is one of the examples Henric referred to better? This is a really simple application. So the less complex, the better.
I just created two applications with one layer of security. Would have preferred to apply security using just one application, but I'm not sure that the data model was compatible.
Thanks!
I just created two applications with one layer of security. Would have preferred to apply security using just one application, but I'm not sure that the data model was compatible.
Thanks!