Skip to main content
Version: 25.3

Custom Content Security Policy headers

Introduction

HTTP security headers are an important part of a website's security posture. They protect against different types of attacks including cross-site scripting (XSS), SQL injection, and clickjacking. Object storage is external to Seqera Platform, and read and write access is strictly limited to a selected group of object storage providers. These select providers are explicitly defined in the Content Security Policy (CSP).

Supported object storage providers

Data Explorer can read from, and write to, the following object storage providers by default:

Subdomain support

If your object storage provider and Seqera deployment share the same subdomain (e.g., minio.janedoepharma.com and platform.janedoepharma.com), then communication between Seqera and the provider works without additional customization. However, if your object storage provider and subdomain don't match, the CSP headers need to be customized.

Connecting additional providers

Accessing new object storage providers in Data Explorer requires updating the Content Security Policy to include the domains to access. This is done by setting the ADDITIONAL_CSP environment variable for the frontend container.

note

This configuration is only available when using the Seqera frontend unprivileged image. If you'd like to use the legacy frontend image, please reach out to Seqera support for further assistance.

Configuration

Set the ADDITIONAL_CSP environment variable with a space-separated list of domains to add to the Content Security Policy. For example, to add support for MinIO:

ADDITIONAL_CSP="https://*.min.io"

To add multiple domains:

ADDITIONAL_CSP="https://*.min.io https://custom-storage.example.com"
info

If your object storage is accessed on a port other than port 80, include the port in the address (e.g., https://myobjectstorage.min.io:9000).