PDF Viewer#

Overview#

Starting with Squirro 3.15.4, the built-in PDF viewer is powered by Nutrient (formerly PSPDFKit). This new viewer improves rendering fidelity, search highlighting accuracy, and performance for large documents.

The Nutrient PDF viewer requires a valid license key to operate. Without a license key, PDF documents are still rendered, but each page is displayed with a watermark.

Note

Existing customers upgrading to Squirro 3.15.4 (or later) must obtain a license key and configure it before the new PDF viewer will operate without a watermark. The PDF viewer also requires additional Content Security Policy directives to load correctly.

Obtaining a License Key#

Squirro provides the Nutrient PDF viewer license key to customers as part of their Squirro subscription. To request a license key:

  • Customers: contact Squirro Support and submit a technical support request.

  • Squirro Delivery Engineers and internal staff: raise a request through the Squirro IT Service Helpdesk.

Once you have received the license key, apply it using one of the methods described below.

Applying the License Key#

There are two supported ways to apply the license key to a Squirro instance, depending on whether the deployment is managed via Ansible.

Option 2: Manual Configuration#

For deployments not managed via Ansible, or as a temporary workaround until the Ansible role is updated, set the license key manually in /etc/squirro/frontend.ini:

[nutrient_pdf_viewer]
license_key = YOUR_LICENSE_KEY

After saving the file, restart the frontend service for the change to take effect. For broader guidance on managing configuration files securely, see the PDF Viewer License Key section of the Secure Configuration Guide.

Content Security Policy#

The Nutrient PDF viewer relies on Web Workers, blob URLs, and WebAssembly, all of which require explicit Content Security Policy (CSP) directives. If your deployment sets a custom CSP, ensure the following directives are present:

worker-src blob:
img-src blob:
script-src 'wasm-unsafe-eval'

For the full recommended CSP policy, see the Recommended Minimal Policy section.