Skip to main content Skip to complementary content

Security

Qlik NPrinting leverages internal and external resources to manage access, authentication, authorization, and data governance.

Platform security

All communication between Qlik NPrinting services and web clients use web protocols using Transport Layer Security (TLS). TLS uses digital certificates to encrypt information exchanged between services, servers, and clients. Encrypted information flows through tunnels requiring two certificates to secure the connection; a server certificate to identify the correct server and a client certificate to allow the client to communicate with the identified server.

The operating system security system controls access to certificates, storage, memory, and CPU resources. Qlik NPrinting uses these controls to protect the platform by only allowing authorized users and processes access to required resources.

For more information about certificates, see Certificates.

Authentication

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, encrypting traffic using TLS and certificates with the following methods:

  • 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 noteIf 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.

Authorization

Attribute based access control provides a comprehensive framework to govern user capabilities within the platform. Data reduction through section access dynamically manages the data which users view and select in applications.

Document Metadata Service (DMS) integrates fully with the existing Directory Service Provider (for example, Active Directory, other LDAP) where Group Membership has been recorded – this is a mechanism by which QlikView Server can re-use existing enterprise accounts and group structures.

For more information about managing role based access controls, see Role based security.

For more information about section access, see Section access.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!