Install
Works with Drupal: ^11.4 || ^12Using Composer to manage Drupal site dependencies
Alternative installation files
Release notes
Upgrading
A configuration import will now fail on a site whose configuration marks a field as gated while storing its files publicly. That combination was previously accepted and silently produced no gate at all, so an import that used to succeed may now stop — correctly. Fix it by setting settings.uri_scheme to private in the exported field storage, or by removing the file_gate.gated third-party setting from a field that is not meant to be gated.
Sites already in that state are reported on the status report after upgrading. Note that changing a field to the private scheme does not move files already stored publicly: they stay where they are, and stay readable, until they are re-uploaded or migrated.
Fixed
A gated field can no longer claim protection it does not provide. Gating applies only to the private file system — public files are served straight off disk by the web server or a CDN and never reach Drupal, so no gate runs.
The field edit form already forced the private scheme when gating was enabled, but that is a form alter and a config-import-authoritative deploy never runs it. So an import could install a field storage carrying file_gate.gated: true alongside uri_scheme: public: the configuration asserting the files were gated, the admin UI showing them as gated, and the files readable by anyone with the URL. Nothing errored, because nothing was broken — the gate simply never engaged.
Two guards, because they reach different sites:
- a configuration-import validator rejects the combination and names the field to fix. It rejects rather than silently rewriting
uri_scheme, which would make a site disagree with its own exported configuration and oscillate on the next export; hook_requirements()reports any site already in that state, which the validator cannot reach.
Changed
The README states the mint trust boundary plainly. It described the cryptography accurately but left an integrator to infer the most important property: mint authorizes nothing. It authenticates the caller with the shared secret and then mints whatever was asked for, with no entity or field access check, so the secret's blast radius is the entire gated corpus. That is a deliberate design — the gate decision is delegated to a trusted back end — but it means the secret must never be provisioned into a tier that serves anonymous traffic.
Two follow-ups are tracked in the issue queue: scoping a signing secret to particular fields, and an optional identity-aware mint.