and29
commented
5 years ago I've faced something similar. My solution was to use windows authentication for Nprinting and creating a task that imports users from the Active Directory (task reads users from LDAP and stores them in excel). I still needed to assign password to the users in Nprinting but it won't be used (since I used Windows authentication), so I assigned a random key large enough.
This link explains how to create the excel for the import. https://help.qlik.com/en-US/nprinting/17.0/Content/Recipients&Users/ImportUsersFiltersGroups/Import-Users-Filters.htm
amien90
We use ADFS authentication for Qlik Sense. And unfortunately On demand only supports NTLM. This means we need to create local account (no connection to AD on the NPrinting server) and supply password to the end-users.
I have no problem with creating the local accounts, but do have a problem with supplying passwords and maintain them. I could work with the same password for all users, but this is not secure of course.
But i wonder if this is possible : create the same password for each user, but that the extension checks if the Qlik Sense UserID is the same as the NTLM that is going to be used for authenticating to NPrinting. in other words, would it be possible for the extension to read the Qlik Sense user, compare it to the NTLM user, and only authenticate the user then Qlik Sense user ID = NTLM user ID.