Authentication in Qlik NPrinting deployments can be managed by proxy service. Upon verification, Qlik NPrinting transfers the user to the Qlik NPrinting Server or NewsStand.

Qlik NPrinting supports the use of Kerberos and NTLM. If you want to use Kerberos authentication, you need to make sure that browsers that are used to access Qlik NPrinting are configured to support Kerberos.

Note: The default authentication module requires that the proxy that handles the authentication is part of the Microsoft Windows domain where Qlik NPrinting is installed.

For more information about Kerberos authentication, see Kerberos authentication.

Traffic is encrypted using TLS and certificates and can be managed with any of the following solutions:

  • JSON Web Token (JWT)

    JWT is an open standard for secure transmission of information as a JavaScript Object Notation (JSON) object. It is used for authentication and authorization. Because JWT enables single sign-on (SSO), it minimizes the number of times a user has to log on to cloud applications and websites.

    For more information about JWT authentication, see JWT authentication.

  • HTTP headers in deployments with trusted systems that transfer user information using this method.

    By default, Qlik NPrinting is configured to use HTTPS for connections with its user interfaces. Qlik NPrinting can be enabled to use HTTP for connections, but HTTPS is the recommended configuration.

    Warning: If you use HTTP instead of HTTPS the data transmitted will not be encrypted. This can pose a security risk.

    For more information about HTTP headers, see Enabling HTTP.

  • Security Assertion Markup Language (SAML)

    Qlik NPrinting supports SAML V2.0. For more information, see Security Assertion Markup Language (SAML) single sign-on (SSO).