Security considerations

The Pixop–Mimir integration is designed to respect tenant isolation. This section summarizes how requests are authenticated and what data is exchanged.

Authentication of custom actions

When a user in Mimir triggers a Pixop-related custom action, the Mimir UI sends a request from the browser to the Pixop integration endpoint.

Each custom action is configured with:

• a shared secret (stored in both Mimir and Pixop), and
• optionally the user’s Mimir token, included in the request if thecustomActionsIncludeMimirUserToken option is enabled.

On the Pixop side we:

1. Verify the custom action secret
   The secret in the request must match the secret stored for that tenant’s integration. This proves that the request comes from a configured Mimir custom action for that tenant.

2. (Optional) Verify the user token with Mimir
   If the integration is configured to include the user token, Pixop uses this token only to call the Mimir REST API on behalf of the user (to get the Mimir tenant of the user (the name of the root folder)).

   • If this call fails, the request is rejected.
   • If it succeeds and the tenant information matches, it adds an extra layer of assurance that the request was triggered by an authenticated Mimir user in the correct tenant.

The token is not stored and is never logged; logs contain only redacted values.

If your security policy does not allow user tokens to be sent to integrations, the Pixop–Mimir integration can be configured to rely solely on the shared secret and tenant configuration. In that mode you still get tenant-level authentication, but not per-user attribution or the extra verification step against Mimir.

Secrets and API keys

• Each integration uses per-tenant secrets and API keys.
• Secrets are generated to be long and random, are only transmitted over HTTPS, and are treated like API keys.
• You can rotate secrets by setting createNewCustomActionSecret=true when updating the integration configuration and thereby the corresponding custom actions in Mimir.

Because custom actions are invoked from the browser, any user who can see the action in Mimir can technically inspect the network traffic in their browser tools. For this reason we strongly recommend:

• limiting access to Pixop custom actions using Mimir’s group/permissions model, and
• using the user-token verification mode when possible, to make it harder to misuse a leaked secret outside Mimir.

Data exchanged between Pixop and Mimir

The integration exchanges:

• item data needed to ingest and process media in Pixop,
• status information and comments written back to Mimir items,
• technical fields related to jobs (IDs, configuration references, status flags).

Logging and monitoring

For troubleshooting and audit purposes we:

• log requests and responses between Pixop and Mimir with sensitive values redacted, and
• log which Mimir user ID triggered actions, where available.