topic Re: Two account through NTName Section Access in QlikView

Two account through NTName Section Access

sridhar_sigired — Thu, 03 Aug 2017 01:04:08 GMT

Hi Experts,

We have few applications deployed in production recently using NTName section access. Recently we got a request from one user asking that he required two accounts to see two set of data from two account through she has only one windows account.

We do not want to use USERID method just for this user, any suggestions how we can implement this?

Thanks,

Sridhar

Re: Two account through NTName Section Access

Anil_Babu_Samineni — Thu, 03 Aug 2017 02:03:13 GMT

I don't think so whether we can add in NTName for that USER. Can you try with plane section access and map to that table for NTName and then check. The idea is if USER has atleast Guest account then you may offer them as they required. I am not sure whether they have two instances for login. Check with then and update the same

Re: Two account through NTName Section Access

sridhar_sigired — Thu, 03 Aug 2017 03:14:38 GMT

Thanks Anil, User has only one log in and she is asking while accessing the dashboard, it should ask for username where we should provide two different usernames for him. So she can log in based on what data set she wants.

I think we can achieve this using USERID (instead of NTName) but we do not want to change our implemented method just for her.

Thanks,

Sridhar

Re: Two account through NTName Section Access

Anil_Babu_Samineni — Thu, 03 Aug 2017 03:21:54 GMT

True, That's not make sense even to me. I tell you the reason behind USER need that. Some users may want to give other credentials with there security level of data. So, here we need to support for them.

Approach -1

If you map to the mapping table passing the parameters and arguments you will achieve that same and do concatenate each together for NTName table and Mapping table (Called USERID)

Approach -2

Either you can create that USER in Active Directory from QMC. and then give grant to that USER specific. This approach is quite straight forward and will work i assume. POS - I don't think if you need data control for this case.

My suggestion to recommend to USER add another account in the same server / machine to access if you don't want to flow which already setup

Does this make sense to you. May be helps to you

Re: Two account through NTName Section Access

arvind_patil — Thu, 03 Aug 2017 03:48:36 GMT

Hi Sridhar,

Concatenation only those record in base table is best way.

Thanks,

Arvind Patil

Re: Two account through NTName Section Access

sridhar_sigired — Thu, 03 Aug 2017 03:49:18 GMT

Please help me on below understanding:

Approach 1: Mapping table means Section Access table?

You mean Existing table have ACCESS, NTNAME and Reduction Field where new table (that is going to concatenate) will have ACCESS, UDERID and Reduction Field? So if we concatenate, only first table names will remain the same. Sorry, i am not if i get it correctly, could you elaborate?

Approach 2: If we create USER in QMC, how that will be mapped with user actual window's ID?

Thanks for your help,

Sridhar

Re: Two account through NTName Section Access

Anil_Babu_Samineni — Thu, 03 Aug 2017 04:19:56 GMT

1) Mapping table nothing but your USERID directory. Something like below

Section Access ....

MappingUserID:

Mapping Load * Inline [

ACCESS, USERID

USER, ABC

];

Concatenate

NTNameTable:

Load ACCESS, ApplyMap('MappingUserID', USERID) as NTNAME;

Load ACCESS, NTNAME From <NTName Excel FIle>;

2) It won't help as expected. But this should work as needed in access point for accessing the files.

HTH

Anil

Re: Two account through NTName Section Access

sridhar_sigired — Thu, 03 Aug 2017 13:44:16 GMT

Thank you guys for your response, i will test it.

Any other suggestions from experts?

Re: Two account through NTName Section Access

Miguel_Angel_Baeyens — Thu, 03 Aug 2017 14:00:57 GMT

This depends on the authorization. If the user is not valid in the directory and DMS is not set, section access will not allow the user to open the application because the user is not properly authenticated. If DMS is set, there will be no prompt, so the user will always be the same, regardless the mapping.

If this user requires two different types of access to two different sets of data either:

she has another domain account created for her (there is a business requirement supporting this, and why fix a user management issue in QlikView when it should be fixed in the user management tool)
or she has access to two different applications, in one she has access to data set A and in the other (which is a copy of the original one, but reduced to her data) to data set B. This somehow addresses a user management issue but is easier in terms of implementation and maintenance, you can even do this from the QMC and create this reduced application