Problems with Section Access

[#1]

I'm playing around with inline section access to test out functionality.  I'm having trouble logging in with USERs.  ADMINs just fine.

here is my code:

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD

    ADMIN, ADMIN, ADMINPWD

    USER, BOB, BOBPWD

];

Section Application;

LOAD * INLINE [

USERID, Representative

BOB, BOB

];

When opening the document using the admin user, it opens just fine.  If I try to use a USER userid, I get "Access denied to this Qlikview document"

Anyone know what I'm doing wrong?  I have reloaded after adding. I have "Initial Data Redectuion Based on Section Access" and "Strict Exclusion" checked.

[#2]

Hi

It is related to your Section Application part, the field Representative should be in UPPER CASE for this to work. But also, that field (and not USERID) should be the one to link to section access table.

Having said that, you only need this field/table if you want to restrict access for Bob to a certain cut of the Data (i.e. to any data that is linked to his name as a Representative. If you don't want to do that then you can remove that part of the implementation.

To protect the document, and simply allow each authorised user to see the whole document, just limit your code to the first part which looks fine to me.

Cheers,

Nigel.

[#3]

Correct, I'm trying to limit access.  So you are saying this where representative is the actual field I want to cut data from?

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD, NAME

    ADMIN, ADMIN, ADMINPWD, ADMIN

    USER, BOB, BOBPWD, BOB

];

Section Application;

LOAD * INLINE [

NAME, REPRESENTATIVE

BOB, BOB

];

And what if I want to give Bob access to two Reps data, is it like this:

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD, NAME

    ADMIN, ADMIN, ADMINPWD, ADMIN

    USER, BOB, BOBPWD, BOB

];

Section Application;

LOAD * INLINE [

NAME, REPRESENTATIVE

BOB, BOB

BOB, TERRY

];

[MayilVahanan]

Hi

Please refer this

http://community.qlik.com/docs/DOC-1853

It helps for section access

[#5]

No.

The field that you want to limit must be in the section acces table and

should contain the limit you want to enforce, I'm guessing that you have

some sales data and Bob is a Sales Rep, you have a dimension for the

sales rep with a column called Representative, and you want to make sure

that Bob only see's data that is "his own".

Also note the following:

Add a Star is * line before all of your code:

The * against the ADMIN line in section access means that this user can

see all data

Note that in the code below I'm aasuming that RepData: is actually what

you have as a dimension table against your data model.

STAR IS *;

Section Access;

LOAD * INLINE [

ACCESS, USERID, PASSWORD, REPRESENTATIVE

ADMIN, ADMIN, ADMINPWD, *

USER, BOB, BOBPWD, BOB

];

Section Application;

RepData:

LOAD * INLINE [

NAME, REPRESENTATIVE

BOB HOSKINS, BOB

];

[#6]

I appreciate the link to the document but I continue to only be able to open the file as admin.  User types get access denied still.

This is my current hidden script:

STAR IS *;

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD, REPRESENTATIVE

    ADMIN, ADMIN, ADMINPWD, *

    USER, BOB, BOBPWD, BOB

];

Section Application;

Reps:

LOAD

     name,

     rep as REPRESENTATIVE;

SQL SELECT  name, rep

FROM mydb.dbo.reps;

[#7]

First, try removing the REPRESENTATIVE part of the section access table,

this will just make sure that your section access code protects the

document and that your problem is in the link to REPRESENTATIVE. Let me

know if this works and we'll move forward, I'll do the same thing on a

test document here.

[#8]

Yes, this works but only if I uncheck "Initial Data Redectuion Based on Section Access" and "Strict Exclusion"

If those are checked I can't even login as a user.

So this is my new hidden script

STAR IS *;

Section Access;

LOAD * INLINE [

    ACCESS, USERID, PASSWORD

    ADMIN, ADMIN, ADMINPWD

    USER, BOB, BOBPWD

];

Section Application;

Reps:

LOAD

     name,

     rep as REPRESENTATIVE;

SQL SELECT  name, rep

FROM mydb.dbo.reps;

[#9]

I just tried your code, it worked fine!

All I did was replace you SQL statement with an inline load, I opened

the document and it asked for a user name and password, I put in BOB,

BOBPWD and the document came up with only BOB showing.

[#10]

On the server, are you using NTFS authorisation?