When run by NPrinting Engine, QlikView apparently consumes a Session CAL and not the assigned Named User CAL

When you use the Desktop client to do Open in Server and connect to a QlikView document using NPrinting's service account, the Named Cal is used as expected.
However, when the qvp connection is executed by the same desktop client with the same account, when launched by the NPrinting engine, it looks a Session cal is used.
The issue only happens when the qvp connection is launched by the NPrinting engine.

The Desktop Client is licensed with a standalone license.
On the QlikView server, Dynamic Named CAL assignment is disabled, one Named CAL is manually assigned to the NPrinting service user 
 

This is an example of the Desktop client launched manually:

f7210cfa-9b04-4c71-bd23-b8813abb6664 RLS64 12.30.20100.0 20190401T110655.000+0200 20190401T110900.000+0200 \\DC1\SHARE\FRONT-END\USERDOCUMENTS\ctrlq.qvw 20190329T175717.000+0200 Socket closed by client 20190401T110857.000+0200 00:00:03 0.005141 2813 8858 26 0 DOMAIN\npservice DOMAIN\npservice QLIKSERVER1 [BA2F0542-FF24-06F0-CC6F-86A1827F9DFD] XXXX YYYY ZZZZ AAAA Windows Exe 12.30.20100.0 On 4747 172.16.16.100 49982 Named User 4f7210cfa-9b04-4c71-bd23-b8813abb6664 RLS64 12.30.20100.0 20190401T110655.000+0200 20190401T110900.000+0200 \\DC1\SHARE\FRONT-END\USERDOCUMENTS\ctrlq.qvw 20190329T175717.000+0200 Socket closed by client 20190401T110857.000+0200 00:00:03 0.005141 2813 8858 26 0 DOMAIN\npservice DOMAIN\npservice QLIKSERVER1 [BA2F0542-FF24-06F0-CC6F-86A1827F9DFD] 3103 5032 6756 8833 Windows Exe 12.30.20100.0 On 4747 172.16.16.100 49982 Named User 4

This is an example of the Desktop client run by the NPrinting Engine:
d50d8a75-ffb5-445b-8fd7-9972078b7759 RLS64 12.30.20100.0 20190401T110655.000+0200 20190401T111201.000+0200 \\DC1\SHARE\FRONT-END\USERDOCUMENTS\ctrlq.qvw 20190329T175717.000+0200 Socket closed by client 20190401T111102.000+0200 00:00:59 0.010948 12165 33410 348 0 DOMAIN\npservice DOMAIN\npservice QLIKSERVER1 [BA2F0542-FF24-06F0-CC6F-86A1827F9DFD] XXXX YYYY ZZZZ AAAA Windows Exe 12.30.20100.0 On 4747 172.16.16.100 50066 Session 6d50d8a75-ffb5-445b-8fd7-9972078b7759 RLS64 12.30.20100.0 20190401T110655.000+0200 20190401T111201.000+0200 \\DC1\SHARE\FRONT-END\USERDOCUMENTS\ctrlq.qvw 20190329T175717.000+0200 Socket closed by client 20190401T111102.000+0200 00:00:59 0.010948 12165 33410 348 0 DOMAIN\npservice DOMAIN\npservice QLIKSERVER1 [BA2F0542-FF24-06F0-CC6F-86A1827F9DFD] 3103 5032 6756 8833 Windows Exe 12.30.20100.0 On 4747 172.16.16.100 50066 Session 6

 

In both cases, the QVS recognized the XXXX YYYY ZZZZ AAAA license, but when NPrinting is involved, a Session CAL is apparently used.
 

Environments:

NPrinting, any

QlikView, any

A bug was submitted to the NPrinting team: OP-8532

Their assessment is that NPrinting doesn't actually use any CAL, since a special channel is used, and that the QlikView logging of a Session CAL is not accurate.

In short: No session CAL is used, despite what the logs say.
 

We have opened a new bug QV-17209 with the QlikView team, to have the logging fixed.
R&D is aware of the problem, but, for the moment, they consider it a low priority issue that won't be fixed for the moment.