Section Access Reload Tasks with Groups instead of UserID

[#1]

Hi all,

Unable to get reload tasks working properly after setting up SA.

I have been researching this problem for a bit and have not found much documentation on implementing SA with Groups as opposed to UserIDs.

I was able to get my section access script to work in the following way:

section access;

Load * inline [

ACCESS, GROUP, GROUP_NAME, OMIT

USER, INTERNAL\SA_SCHEDULER, *,

USER, FREMONT\ADMIN,  *,

USER, Developers, *,

USER, Singapore,  "SINGAPORE",

USER, Europe, "EUROPE",

];

The first access line in my section is what you use for the system to schedule a reload task when implementing with users. Does anyone know how to implement the italicized line when using Groups?

Thanks!

[marcus_sommer]

Instead of GROUP you need to use NTNAME and there you could use the NT group-names. And I would give at least the qv-services user and your main development user ADMIN rights by ACCESS. Further helpful might be: Section Access.

- Marcus

[#3]

Marcus:

NTNAME gave me reload tasks back but broke section access. Is there a prefix I'm supposed to have before the group name? The groups are set up through Active Directory. But I'm not sure how Qlik addresses the names of the groups.

For example, for username, it has a prefix eg. SERVER/username

Is there such a prefix for user groups created with Active Directory?

[marcus_sommer]

It could be that you need the domain like: DOMAIN\UserGroup

- Marcus

[avkeep01]

Hi,

Marcus_Sommer I tried it with the prefix but it doesn't work. The section access is based on the groupname and the NTNAME or USERID isn't identified. Is it possible to put the SA_SCHEDULER into a group? right now i'm not able te reload the data.

- Anton van Keep

[marcus_sommer]

It's always good to put a textbox with osuser() on the surface to see how the login-user will be identified - with local machine + on the server + access point. With SA_Scheduler you mean the user-account from the qlikview-server services? If yes it's necessary to put them into the section access with admin rights.

- Marcus

[avkeep01]

The textbox with osuser() is a good idea.

One of the problems is the use of a virtual proxy to identify users. That means that the users don't exist on the server. So using NTNAME isn't working.

I need to put in the SA_Scheduler but i can't identify it based on a group, only on NTNAME or USERID, but those two aren't a possibility for the users.

[marcus_sommer]

Your environment sounds quite uncommon - I suggest before going further to collect all requirements again and rethink the whole environment and if it's really necessary to use a rather uncommon or heavily customized implementation of authentication and autorization - to consult professional help (you will save a lot of time and money to get the things right instead of curing strange symptoms).

- Marcus