Install

Works with Drupal: ^11.4 || ^12

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 192.93 KB
MD5: 26d1ddb1051f56391b4360fb8cfc3dc1
SHA-1: 81340c1ee82b3cce20f77bd58423e1b9b498a575
SHA-256: f1add3b6f7b1c427ee7f2afd552017d9a52f78d8861478422dd06aca08a14402
Download zip 283.95 KB
MD5: d6b7dbc8f976b5b71fe2d5a51fac625c
SHA-1: 8dfb88aa80a871ded4dcf3e7eac28f9bfebf7ed5
SHA-256: a987724166ce8abb5cdcd62b59ed8dfff05cdca2739525701663307820845d25

Release notes

Added

  • Multiple trusted issuers for the assurance method (#3614673). The assurance gate method accepts a trusted_issuers list — each entry with its own issuer URL, expected audience, and accepted acr values — so one gated field can serve users from several identity providers. A presented token matches exactly one entry by its iss claim: no cross-matching between entries, no fallback when none matches, and unknown issuers are denied without any discovery traffic. Existing single-issuer settings keep working unchanged as a one-entry list.
  • Site-relative step_up_login_url (#3614675). The step-up login target may now be a site-relative path (single leading slash) as well as an absolute http(s) URL, keeping exported configuration environment-neutral when the site provides its own step-up initiator route. The open-redirect defenses are unchanged.

Changed

  • Clearing a managed assurance setting in the field form now actually clears it. Previously an emptied value could leave the old stored value silently in effect.

Fixed

  • The step-up page validates the stored token shape before building the Authorization header (#3614534) — a malformed token now shows an actionable message instead of a cryptic fetch error.
Created by: jmcerda
Created on: 3 Aug 2026 at 17:09 UTC
Last updated: 3 Aug 2026 at 17:09 UTC
Bug fixes
New features
Unsupported

Other releases