QDC/QS AD users: different “UserID” format

[Br1]

Hi,

We have a single node installation of QDC September_2019_SR2.

We are setting Qlik Sense integration to enable "Publish to Qlik" feature and we experience the following blocking issue.

Both QDC and QS are synchronized with our AD, but referring to the “UserID” field, QDC populate its database considering username and domain name (UserID=username@domain.local) while QS register only the username (UserID=username).

I attach screenshots from both applications (attachments 1 & 2).

Considering the above, any domain user who wants to use the “Publish to Qlik” feature, will cause the following:

• the QDC entity will be published using the UserID in QDC format (UserID=username@domain.local) who on QS side becomes the owner of the object;
• ever during the publication phase, the above UserID is passed from QDC to QS which fails to recognize it in this format and proceeds by creating a new entry in the Users list (see the attachment 3);
• at the end of the publication phase, QDC would like to open automatically (using a QS URL) the App just published but without success, also in this case due of the UserID inherited from QDC during this process;
• the user who log in QS (or who is already logged in) with his own AD credentials is recognized in the QS format (UserID=username) and will never see the objects published via QDC (which in fact have a different UserID owner).

As proof of the above, if I proceed by setting a specific Username for the “podium.qlik.username” entry in the “core_env.properties” file, all works properly (obviously the user must respect the format of Qlik Sense).

How is it possible to have QDC “UserID” list populated in the same format as QS “UserID” list (UserID=username) during synchronization with AD?

Which settings need to be changed?

Your suggestions will be greatly appreciated.

Regards

Bruno

[Anonymous · Accepted solution]

Hi Bruno,

So Alex Colombo created a fix and you can add this code to any of the applist.js, createQlikApp.js and updateExistingApp.js scripts to fix your problem.

This will make sure that you only use username if its in the format of username@domain.com:

var userId = process.argv[4];
var nameParts = userId.split("@");
var userId = nameParts.length==2 ? nameParts[0] : userId;

or if you would like to deconstruct 1stname.lastname@domain.com into a lastname1stname format:

var userId = process.argv[4];
...
var dot = userId.indexOf(".");
var at = userId.indexOf("@");

var name = userId.substr(0, dot);
var lenghtSurname = at - dot - 1;
var surname = userId.substr(dot + 1, lenghtSurname);

userId = surname+name;

 Does this help?

Best,

Hordy

[Br1]

Hi Hordy, Alex,

I just tried by adding your fix code of 1st scenario (QS use only username as UserID) to the createQlikApp.js

var userId = process.argv[4];
var nameParts = userId.split("@");
var userId = nameParts.length==2 ? nameParts[0] : userId;

Now the "Publish to Qlik" feature works properly!

Thanks

Regards

[Br1]

Hi Hordy,

could you please ask your Technical Support team to make the fix available in the next QDC release?

Obviously if it doesn't already exist in version 4.4.2 (in the Release Notes I found only the ID note n.11588 which is not so clear about it).

Thanks again!

Best regards

Bruno

[Anonymous]

Hi Bruno,

I have let the product team know and they are working on a fix to make it customer configurable.

Best,

Hordy