NPrinting 17.x and Alternate IdentityArticle Number: 000024381 | Last Modified: 2018/06/12
Local files and server/cluster connections should be considered separately.
In local files the only supported alternate identity is the one defined in the Section Access tables of the document and just USERNAME/PASSWORD is supported, not NTNAME.
In server/cluster connections both alternate identity with and without Section Access tables are supported and in this case you don't need any password (if with Section Access just NTNAME, without USERNAME and PASSWORD are supported) OR section access with just USERNAME/PASSWORD but the user running the engine service must be able to access the document on the server.
So, as an example, the connections should be configured with "Connection requires authentication", then "Server authentication" and in Identity "DOMAIN\userid". The checkbox "Apply user section access for reports".
This will work, but all the other requirements like the following must be fulfilled.
- The engine service user must be in QlikViewAdministrators in each QLIKVIEW server machine (if you will use the cluster it must be also in the management api group)
- The identity configured must have the right permissions configured on the file
- The server must use NT authentication.
We don't need passwords when users are domain users and we don't support "Section Access" with DMS or QlikView Document users.
The only supported configuration for Section Access is domain users with the necessary setup to allow NT impersonation.
The only supported configuration for simple Document Authentication is QlikView Document users with the necessary setup to allow QlikView and its running Windows user to open the document without requiring further credentials.
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.