SECTION ACCESS: How to deal with different domains for UserID for Test, Dev, Prod environments?

[jblomqvist]

Hi,

We have three environments, Test, Dev, and Production.

For each environment we have a different domain for the USERID field in Section Access.

So for example:

In Test my USERID could be GLOB\JB001

In Dev my USERID could be DEVT\JB001

In Prod my USER ID could be PRODT\JB001

Am I correct that the domain must be included as part of USERID in Section Access?

Is there a way maybe I can wildcard and do something like *\JB001 for my USERID field?

We want to remove this problem of having to change USERIDs whenever we move the app into different environments.

Any good solutions you can think of?

[marcus_sommer]

Are this really different users from a NTNAME point of view? If not a change to it might be already a solution (in general I suggest to consider of using NTNAME instead of USERID).

Beside this you could check with computername() on which environment the scripts are running and changing with it the domain, for example:

...

pick(wildmatch(computername(), 'GLOB*', 'DEVT*', 'PROD*'), 'GLOB', 'DEVT', 'PROD') &

     '\' & USERID as USERID

...

- Marcus

[manoj217]

create config file

[jblomqvist]

Hi Marcus,

Tack for replying.

Is it possible to use NTNAME in Qlik Sense? Can you share an example please?

Also, does Qlik Sense require the Directory part in the Directory\UserID format for User IDs? I.e. Is it mandatory? I was wondering if Qlik Sense would work simply using the IDs in the UserID field.

[marcus_sommer]

In general the logic of NTNAME is available but it seems that there are some changes against the implementation in QlikView and that NTNAME = USERID. I never worked with the Sense section access but here you could find some information: Tips and tricks for section access in Qlik Sense (2.0+)

I'm not an expert on the active directory stuff which is behind this authentication-method but I could imagine that there are scenarios possible in which the authentication could work even with multiple domains - but honestly my second suggestion with the pick(match()) approach of building the right USERID should be much faster to implement.

- Marcus