Qlik.NPrinting.Scheduler.exe nicht digital signiert?

[C-Hopf]

Hallo zusammen,

ich habe von einem Kunden folgende Fragen bekommen: 

1. Ist der Prozess Qlik.NPrinting.Scheduler.exe Bestandteil der offiziellen Qlik-NPrinting-Installation? (Ja)
2. Führt der Scheduler regelmäßig LDAP-Abfragen gegen das Active Directory durch (z. B. für Benutzer-, Gruppen- oder Rechteauflösung)? (Ja)
3. Für welche konkreten Funktionen werden die LDAP-Abfragen benötigt (z. B. Report-Verteilung, Benutzerabgleich)? ?
4. Ist bekannt, dass die ausführbare Datei nicht digital signiert ist? ?
5. Betrieb & Best Practice? ?

Die beiden ersten Fragen sind klar, aber ich bräuchte Hilfe bei den weiteren Fragen.

br

Christian

[David_Friend]

@C-Hopf I did a Google translate of your post, but in the future please post in English, also that number 5 super broad and generic, and for number 4 to suggest product improvements you can go here:

https://community.qlik.com/t5/About-Ideation/ct-p/qlik-aboutideation

[Lech_Miszkiewicz]

So for others to actually understand what this is about:

Hello everyone,
I received the following questions from a client:

1.Is the process Qlik.NPrinting.Scheduler.exe part of the official Qlik NPrinting installation? (Yes)
2. Does the scheduler regularly perform LDAP queries against Active Directory (e.g., for user, group, or permission resolution)? (Yes)
3. For which specific functions are the LDAP queries required (e.g., report distribution, user synchronization)?
4. Is it known that the executable file is not digitally signed?
5. Operation & Best Practices?

The first two questions are clear, but I need help with the others.
br
Christian"

My comments:

@David_Friend - now we dont have to translate each time someone wants to comment

@C-Hopf - Answering your questions:

3. LDAP queries are not required. You can load and manage your NPrinting users by use of  external files (XLSX). LDAP query can be used as an alternative to load users to NPrinting. Users become recipients of the reports when NPrinting runs so that is main purpose of being able to maintain who gets report. Obviously you can also create users manually and you dont have to import them at all (neither via XLSX or LDAP). More about users here:

• creating: https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/Recipients&Users/Create-users-f...
• importing: https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/DeployingQVNprinting/Import-Use...

4. As David mentioned - you can create idea to get those signed

5. Operation & Best Practices - there isn't one way of doing things. With NPrinting you have to have understanding and knowledge of your Qlik app (how data is structured in data model, how associations are working, what data types are used (very important for filters) and of course how UI objects are built. This knowledge is important as you need to cross check it with what is and isn't supported with NPrinting. Then you need to know what you are trying to achieve regarding your report (its output file type, layout, required formatting and delivery method). This is critical and I often say that NPrinting development is 90% in QlikView or in Qlik Sense and remaining 10% is in NPrinting. Once you know that you need to have a knowledge about limitations of each of the available template formats (Entity, HTML, PixelPerfect, Word, PowerPoint and Excel) and think in which of those you would spent least time creating something what would be best suited. One example of such thing could be requirement of having conditionally formatted table with editable data. Straight away the only reasonable solution is excel template as all other templates don't support conditional and editable output. The other example is use of variables in UI objects controlled by buttons or variable inputs. In task distributed reports those can be set as variable filters but if you would like users to use OnDemand functionality with users selecting values from UI that would not work as OnDemand does not support variable inputs.

I could keep writing about this for ages. From my experience I can tell that people underestimate how important abovementioned knowledge is and often build something what is slow and not reliable or something what is not supported and does not work. There is also perception that it is "just" NPrinting running on top of Qlik Apps and people think that they will not have to touch Qlik Apps to do development in NPrinting. That is very wrong assumption and it should be very opposite. People should assume that they will have to first develop Qlik apps/sheets for the purpose of NPrinting and often they will have to do development in load script in order to make required changes to model which can be used in NPrinting report.

That is my 5 cents regarding this.

cheers

[C-Hopf]

Thank you for the replies.

One Question, what about the ServiceUser communicating with the other Qlik Servers?

Does it communicate also with the LDAP?

[Lech_Miszkiewicz]

Hi @C-Hopf

Service account for NPrinting as documented must be domain account. As such it goes through a process of authentication (NTLM authentication). https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/DeployingQVNprinting/User-accou...

So, for example - Do you consider communicating with LDAP when you as @C-Hopf are logging in to the server and you use your credentials to login? If yes then you have your answer as the same will happen with service accounts.

there you have it

cheers