Authentication in Qlik NPrinting deployments is managed by the Qlik NPrinting web engine, which verifies user identities before allowing access to the Qlik NPrinting Server or NewsStand.
The standard entry points for Qlik NPrinting web console and NewsStand are configured to use HTTPS for connections with their web interfaces. Traffic is encrypted using TLS and certificates. HTTPS is the recommended configuration, because it is more secure. However, Qlik NPrinting can be configured to use HTTP in environments that requires it, like when it should work behind a reverse proxy. For more information about HTTP, see: Enabling HTTP.
Qlik NPrinting supports the use of username and passwords or Kerberos and NTLM as integrated authentication methods. They are managed internally by the Qlik NPrinting web engine.
To enable Windows login, open the user profile and add the domain\username.
Do the following:
- From the Admin menu, click Users.
- Select the user you wish to edit.
- Fill in the Domain account field: Enter the domain and user name.
A user must have an associated domain account to use the following features:
- Receive reports in Qlik Sense hub.
Create On-Demand reports in QlikView.
The user's Windows Active Directory user account must be associated as the domain account.
You can disable Windows login by going to Admin > Settings > Authentication.
If you want to use Kerberos authentication, you need to make sure that browsers used to access Qlik NPrinting are configured to support Kerberos. See: Kerberos authentication.
Qlik NPrinting supports the following external authentication methods, managed by the Qlik NPrinting web engine:
JSON Web Token (JWT)
Security Assertion Markup Language (SAML)
Qlik NPrinting supports SAML V2.0. For more information, see: Security Assertion Markup Language (SAML) single sign-on (SSO).