file_gate 1.13.0

New features

A site can coordinate usage-limited Signed URL and Assurance grants with a host transaction for a named credential and field. File Gate still signs, spends, and revokes the grants.

This optional integration provides scoped transaction participation and primary grant-state inspection. Existing grant behavior remains the default when the integration is not selected.

file_gate 1.12.1

Bug fixes

### Changed
- Assurance operator docs match shipped fail-closed `allowed_subjects` (empty
denies), list all four `verify_at` values, and state that WebAuthn enrollment
RP comes from `$settings['file_gate.webauthn']` (or JSON `rp`), not the field.
Field settings forms no longer show ticket ids in descriptions.
- Assurance design note `docs/design/piv-cac-webauthn.md` now matches shipped
defaults: `verify_at: redeem` (Model B, plain-link + `FG_AB` session bridge).
A1 remains trust-the-secret-holder (`verify_oidc_at_mint` off); A2 stays

file_gate 1.12.0

Bug fixes
New features

Changed

  • Use independent changelog fragments for pull requests and the shared validator for lossless release preparation.
  • Install config now ships an empty introspection_client_secret to match schema. ADR usage-limit wording matches GrantLockTrait / SECURITY.md (locked, fail closed). CONTRIBUTING phpcs uses phpcs.xml.dist; phpunit covers unit tests and submodule suites.

file_gate 1.11.6

Bug fixes

### Removed
- Unused GET `/api/file-gate/webauthn/credentials` (`listCredentials`) and
unused `userHandle` in enrollment `drupalSettings`. The account form lists
credentials server-side; enrollment JS never reads `cfg.userHandle`.
- Drupal 10 `hook_requirements` bridges from `file_gate_assurance` and
`file_gate_commerce`. Both submodules require `^11.4 || ^12`, so the
`#[LegacyRequirementsHook]` shims never ran. The base module still
keeps its Drupal 10.6 bridge.

file_gate 1.11.4

Bug fixes

## [1.11.4] - 2026-10-14

### Security
- **Token redeem pins the signed/stored field.** Token `allowsField()` now
uses `MintStoredField::pin()` (signed `fld`, else the token-store row),
matching download, signed URL, and the assurance bridge. An unsigned JSON
body `field` / `fld` is ignored. `fromSignedClaim()` is private to `pin()`.
The README trust-boundary section no longer claims identity-aware mint
and field-scoped secrets are unbuilt: both are shipped opt-in
constraints, not a default ACL.

file_gate 1.11.2

Bug fixes

## [1.11.2] - 2026-10-02

### Changed
- Drupal.org GitLab CI stays green. The project cspell dictionary covers
the module's unknown words, and the previous-major composer lane no
longer fails the pipeline.

file_gate 1.11.1

Bug fixes

### Fixed
- Unlimited signed URL grants (`max_uses=0`) pin the mint-resolved field as a
signed `fld` claim. Redeem has no inventory row for those grants, so
`allowsField()` used unpinned `getGateForFile()` and could pick another
`signed_url` field on the same file. Scope now follows the HMAC-validated
claim (`referrer_lock` and `assurance` inherit). An unsigned `field=`
query, a JSON body `field`, and a `token` query cannot select another
field's settings while `fld` is present. OTP issue still reads its body

file_gate 1.11.0

New features

### Changed
- https://www.drupal.org/project/file_gate/issues/3627119: Support the base module on Drupal 10.6/PHP 8.2 and Drupal 11.3/PHP 8.3. Older core uses a revision-aware file-reference backport; Drupal 11.4 retains the native resolver. Historical references, field authorization, download refusal and runtime security findings retain their existing rules. Optional submodule requirements remain unchanged.

file_gate 1.10.5

Bug fixes
Unsupported

### Fixed
- Redeem pins the mint-stored field. Download, signed-url and token
`allowsField()` checks, OTP, and the assurance bridge / WebAuthn
controllers called unpinned `getGateForFile()`, which picks the
lexicographic winner among two `signed_url` fields. A named secret
scoped to `field_whitepaper` then failed scope against `field_nda`.
Scope now follows the field stored on the grant row.

file_gate 1.10.4

Bug fixes
Unsupported

Fixed

  • Mint stores the field resolved for that request. Signed URL and token grants had called the resolver again while recording the grant, which can select a different field of the same method when one file sits on two gated fields. Revoke scope now follows the field that minted the grant.

file_gate 1.10.3

Bug fixes
Unsupported

### Fixed
- A stored `download_flood_limit` of 0 now disables the per-IP deny flood.
The controller had read the limit with `?:`, so 0 fell back to 120 even
though the settings form and schema already treat 0 as off. A missing
limit still defaults to 120.

file_gate 1.10.2

Bug fixes
Unsupported

### Fixed
- MCP grant revoke lets `GrantInventory::revokeJti()` size the kill mark.
The tool had passed its own `max(DEFAULT_KILL_TTL, remaining + 3600)`,
which ignored a kill mark already stored for that grant.

file_gate 1.9.1

Bug fixes
Unsupported

Fixed

  • Single-jti revoke now drops grant inventory. `POST /api/file-gate/revoke` with `{"jti":"…"}` spent the grant but left it listed on `GET /api/file-gate/grants` until natural expiry. Both revoke paths now share one `GrantInventory::revokeJti()` helper that writes the spent counter and `forget()`s the row. The default kill-mark TTL is 30 days on both paths (single-jti was 24 hours).

file_gate 1.9.0

New features
Unsupported

Removed

  • Dead public helpers on the mint/OTP/assurance path. FileGateAudit::isAvailable(), OtpSession::boundEmail(), SessionOidcToken::isAvailable(), and SessionBridge::clearCookie() had no callers. OTP grants() no longer reads a POST body for email/otp — the download route is GET-only; query and FG_OTP cookie redeem are unchanged.

Changed

file_gate 1.7.0

New features
Unsupported

Added

Identity-aware mint now checks user hosts, field view, and nested parents (#3618403).

  • Acting-account mint requires file download access, view access on every referencing host (including a user entity), view access on the referencing field, and view access on each getParentEntity() ancestor when the usage host is a child (paragraph / inline).
  • A gated file with no resolvable host is refused.

file_gate 1.5.2

Bug fixes
Unsupported

Fixed

  • Assurance token endpoints beside simple_oauth, correctly this time (#3614535). The 1.5.1 _auth: ['cookie'] route pin is inert for this failure: global authentication providers authenticate before routing, so they 401 a foreign Bearer token before any route option is consulted. A new AuthorizationShield http middleware stashes the Bearer/DPoP Authorization value into a request attribute and removes the header on File Gate's own token endpoints (/api/file-gate/download, /api/file-gate/assurance/bridge) before any provider runs; handlers read the stash transparently. Clients keep standard Authorization: Bearer/DPoP wire semantics — no client changes. Basic (service-secret) credentials and all other routes are untouched. Behavioral regression coverage in both directions.

No update functions; no configuration or API changes. Safe drop-in update from 1.5.0/1.5.1. Sites running simple_oauth should update immediately — the assurance token redeem path does not work without this.

file_gate 1.5.0

New features
Unsupported

SSO session bridge, OTP session cookie, grant inventory, commerce SKU entitlement, campaign token TTL, IdP ACR helper.

file_gate 1.4.0

Bug fixes
New features
Unsupported

Security

  • Step-up open redirect closed (#3614254): only field step_up_login_url is used; query login_url is ignored.
  • OTP HMAC uses authenticated secrets (#3614253), including dual-key previous materials during rotation.

file_gate 1.3.0

Bug fixes
Unsupported

Security

  • Plain-link high-assurance path (#3612909). Open the signed download URL; complete OIDC step-up (optional DPoP); a short-lived HttpOnly cookie (FG_AB) lets the same plain URL stream the file. HMAC and usage limits still apply. API clients receive a 401 challenge with WWW-Authenticate.

file_gate 1.1.0

Bug fixes
Unsupported

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.

file_gate 1.0.2

Bug fixes
Unsupported

Declares the PHP floor in composer.json. No code change; nothing to do on update.

Changed

composer.json now declares "php": ">=8.3". It previously specified no PHP constraint at all, so the effective floor came only from whatever core happened to require — the supported surface was implied rather than stated, and a reader had to trace Drupal's own requirements to find it.

file_gate 1.0.1

Bug fixes
Unsupported

Fixes a fatal on PHP 8.3, which is inside the supported range. Sites on 11.4 running PHP 8.3 should update.

file_gate 1.0.0

Unsupported

File Gate 1.0.0 — the first stable release.

File Gate gates delivery of private files behind pluggable gate methods and streams them through its own signed endpoint, for decoupled and traditional Drupal alike. Five core methods ship (signed_url, authenticated, token, referrer_lock, otp), plus three optional submodules (Form, Commerce, Assurance).

file_gate 1.0.0-rc1

Bug fixes
New features
Unsupported

File Gate 1.0.0-rc1 is the first release candidate for the 1.0 line. It is feature-complete: every planned gate method has shipped. It is published as a release candidate so the new security-sensitive code (HMAC signing, OIDC/JWT, DPoP, one-time passcodes, entitlement checks) can be exercised in the field before a stable 1.0.0. Kernel-tested (99 tests); no known open issues.

file_gate 1.0.0-beta1

Unsupported

Initial beta release. File Gate denies anonymous access to private:// files and delivers them only to visitors who have passed a gate — a lead form, a login, a token — through short-lived signed URLs that work with any front end.

Out of the box, Drupal grants a private-file download to anyone who can view the entity that references it; because anonymous users can view published content, a private file attached to published media is effectively public to anyone who has the link. File Gate closes that gap.

file_gate 1.0.x-dev

Initial release. File Gate denies anonymous access to private:// files and delivers them only to visitors who have passed a gate — a lead form, a login, a token — through short-lived signed URLs that work with any front end.

Out of the box, Drupal grants a private-file download to anyone who can view the entity that references it; because anonymous users can view published content, a private file attached to published media is effectively public to anyone who has the link. File Gate closes that gap.

Subscribe with RSS Subscribe to Releases for FileGate