Skip to content
Menu

Changelog#

All notable changes are listed here. The format follows Keep a Changelog.

Unreleased#

  • Docs: the README says the accessibility checker is vendored from Preflight 0.9.0 (it said 0.5.0), the copy CI pins. Content only.
  • Changed: deploy/ requires PROCTOR ^0.16 (was ^0.15, which does not allow 0.16), whose ci-pipelines check no longer asks for a GitHub workflow (D-069).
  • Changed: the deploy kit is Squire 0.11.1 (was 0.10.7): the release script fetches PROCTOR when --no-dev left it out and installs the frontend from a yarn.lock, the HAProxy pin is current, the fallback base follows the app's PHP line, and the parity scripts carry the deprecation note.
  • Changed: CI pins Preflight 0.9.0 (components and the a11y checker copy).
  • CI: the GitHub workflow calls Preflight 0.9.0's reusable workflow (commit fb73b53), the release the GitLab pipeline pins.
  • Added: drawbridge smoke checks a running gateway from the outside without signing anyone in, the first command to run after a deploy, a restart or a rollback. It asks /_drawbridge/up, a host that is not configured (403), and for each app a login path (a redirect to the provider carrying the redirect URI, client id and PKCE the config and DRAWBRIDGE_PUBLIC_SCHEME imply, which is the URI Entra must have registered), an api path (a bare 401), a deny path (403), a public path (the app answers, so the upstream is reachable, and spoofed identity headers sent with it never arrive), a made-up callback (no session) and /metrics (403 to a stranger, 200 to DRAWBRIDGE_METRICS_TOKEN, and the version it reports). Read-only; exit 1 when a check fails, --format=json for a test record. Inside the container every default is right: docker exec <gateway-container> /opt/drawbridge/bin/drawbridge smoke. The rig runs it both ways: in-process against the gateway (SmokeTest, which also shows it fails when pointed past the gateway at the app, or with the wrong public scheme) and inside the gateway container with no options, after every default rig run.
  • Fixed: /metrics reported drawbridge_build_info{version="1.0.0.0"} from the gateway image, Composer's guess for a tree with no git metadata, instead of the release. The CLI and the gauge now read one constant, Version::CURRENT in src/Version.php, and VersionTest keeps it equal to the newest release heading in this file. Found by the smoke check's first rig run.
  • Added: the trial kit in trial/, the smallest real deployment for a first run on a pre-production host. It has a compose file with the gateway and a throwaway whoami app on the same image (no capabilities, no new privileges, read-only mounts, rotated logs, the gateway on loopback only, whoami unpublished), an example config with one path of every kind, an .env.example with the secrets left empty, and whoami itself: one PHP file that verifies the assertion with openssl and shows what it checked. The new guide First deployment walks it: the files and keys, the compose and docker run shapes, health, the smoke check, logs, metrics, a rollback (up -d --no-deps gateway) and the teardown.
  • Rig: sh rig/run.sh trial (rig\run.ps1 trial) runs the trial kit as shipped, with the mock provider added. It signs in through whoami, sends whoami a forged assertion around the gateway (refused) and runs the smoke check. Then it rolls the gateway back to another image and checks that whoami was not recreated and that both checks still pass (TrialTest). TrialConfigTest keeps the kit's config, compose hardening and .env.example honest. Both CI rig jobs run it too, and the Proof page has a section for it.
  • Added: on an https host the smoke check's login line also reads the state cookie the sign-in redirect sets, and fails when it lacks Secure: the gateway marks the session cookie the same way, and a __Host- session cookie without Secure is dropped by every browser. A gateway that misreads its scheme behind the front proxy now shows up before anyone signs in. A login answer of 500 names the likely cause, the provider's metadata (a wrong oidc.issuer or no outbound HTTPS).
  • Changed: the smoke check's public-path line says "the app saw none of the spoofed identity headers" (it said "the echo app", whichever app answered).
  • Added: the smoke check's clock line compares the app host's clock with the gateway's, from the Date headers of the app's answer on a public path and of the gateway's own /_drawbridge/up (Apache keeps a proxied Date). An assertion lives 60 seconds and SESAME allows 30 seconds of skew, so more than 10 seconds apart fails, before any assertion is refused (BEST_PRACTICES.md D42; host time sync is still the platform's to confirm). SmokeClockTest covers the pass, the early warning, the refusal, and the skips.
  • Docs: the Overview's "Pick your path" and "Related" lists link First deployment, so the docs' front door reaches it, not only the guides and references that mention it.
  • Site: a new front-page sheet, A-602 Field inspection, shows drawbridge smoke as an inspector's field report: one stamp per finding in the command's own wording for the example config's app1, a verdict stamp, and three mistakes to try (a wrong tenant, a misread scheme, a drifting clock) that swap in the failing line and exit 1. Beside it, the trial kit's eight steps and a link to First deployment. The drafting kit lists smoke, the rig paragraph and the revision table mention the trial kit, and the specs sheet is now A-603.

0.6.2 (2026-11-10)#

  • Fixed: the gateway image is built for linux/amd64, the architecture of Citadel's docker hosts. The gateway-image:publish job now carries the amd64 runner tag; 0.6.1's image was built on an arm64 runner and does not run on Citadel.
  • Docs: the Where it fits tables no longer say Parity 0.1.0 is coming (it is out).
  • Docs: the README names the Preflight checker version the a11y gate actually vendors (0.5.0).
  • Changed: the deploy layer requires PROCTOR ^0.15 (locked 0.15.0, was ^0.12): 0.13 checks the release cooldown against the CREED policy, 0.14 adds script-pair and 0.15 adds mysql56-ci; all only warn, nothing breaks.
  • Changed: the GitHub workflow calls Preflight 0.5.0's reusable workflow (pinned to its release commit), the same release as the GitLab pipeline; it was on 0.1.4 because GitHub's copy of Preflight had no later tag.
  • Changed: the deploy layer requires PROCTOR ^0.12 (locked 0.12.0, was ^0.11): two new warning-only checks, nothing breaks.
  • Site: the front page's stale facts are current (the party list links Parity's site; it no longer says "site coming").
  • Changed: the deploy kit is Squire 0.10.7 (was 0.10.6): it ships a .gitattributes that pins line endings, so the deploy layer clears PROCTOR's line-ending warnings.
  • Changed: the docs, agent-ready and deploy kits are Squire 0.10.6 (was 0.10.5): the docs builder and agent-ready generator see every file on Docker Desktop mounts.
  • Site: assets/stack-env.js knows Parity, so a pre-production page links Parity's pre-production site and a dev page links its local site/ folder. Until now Parity, of all parts, was the one link that ignored its environment.
  • Rig: sh rig/run.sh multi (rig\run.ps1 multi, and a step in both CI rig jobs) rolls a crypto passphrase change across two gateway instances on one Redis: once both hold the new and the old value a session either one seals opens the app on the other, once the old value is gone both send its sessions to sign in, and mid-roll an instance still on the old value sends a session sealed under the new one to sign in; rig/run.sh now also runs from Git Bash on Windows (MSYS_NO_PATHCONV=1).
  • Changed: CI's rig job also runs the redis and redis-rotation modes.
  • Deploy kit refreshed to Squire 0.10.5.

0.6.1 (2026-11-09)#

  • Docs: the upgrading guide has a 0.6.1 section (no breaks; the gateway image's Apache and module floors do not change), and the README, docs, CLI version, gatehouse drawing and front page say 0.6.1.
  • Changed: CI pins the Preflight components to 0.5.0 (was 0.4.0), and the composer-audit job takes the component's own image instead of naming one; the a11y pin test expects 0.5.0 (the a11y template is the same in both).
  • Docs: Parity joins the party. The README cast and "Where it fits in the stack" table, the docs overview, How it works and the front page's key plan carry Parity next to Squire, with its spirit-level mark: the stack's new tool that runs Citadel on your computer (its PHP image, its proxy and MySQL 5.6). 0.1.0 is coming and it has no site yet, so its entries link nowhere. A scale model of the castle, built on the level.
  • Changed: refreshed version mentions. The "Where it fits in the stack" table in the README, the docs overview and How it works now seats the whole garrison in the cast's order (Squire, Booster, Rollcall, ADVISOR and WELD were left outside the walls), and the dev dependency Pinstripe moves to ^0.3 (locked 0.3.0; it bans joined SQL and turned-off TLS checks).
  • Changed: the wayneui-copies, composer-ci and advisories CI jobs, the rig's install step and the documented Docker commands run Composer 2.11.1 (was 2.10.3, no longer maintained), pinned by its multi-arch list digest; 2.11 fixes GHSA-c968-33g3-wh7p and GHSA-fm2w-xgf2-f9fh.
  • Changed: the front page deploy kit is Squire 0.10.2 (was 0.10.1): the kit's php.ini sets session.cookie_samesite = Lax, the fallback base names its images in full (docker.io/library/...) with Composer as a build argument, and the portable image drops node_modules/ after the build. The gateway image does not change.
  • Changed: the front page deploy layer requires HELMET ^1.3 (was ^1.0) and CREED ^0.1.8 (was ^0.1), and its lock moves to HELMET 1.3.0, CREED 0.1.8 and PROCTOR 0.11.1; the dev dependency Pinstripe is ^0.1.4 (was ^0.1, locked 0.1.0, now 0.1.4).
  • Docs: MAINTAINING names the maintainer as a role, reached through an issue on git.wayne.edu, and the test and CI comments say what they hold in plain words instead of internal item numbers.
  • Rig: sh rig/run.sh redis-rotation (rig\run.ps1 redis-rotation) proves a crypto passphrase change over the Redis session store signs nobody out: a session from passphrase A survives a reload with B current and A previous, a new sign-in works under B, once A is dropped its session is sent to sign in (not a 500), and the B session survives a gateway restart; the docs and the front page drop "expected, not proven" and the README and Sessions guide gain the three rotation steps.

0.6.0 (2026-11-09)#

  • Changed: the deploy kit is Squire 0.10.1 (was 0.10.0): the fallback base image copies Composer 2.11.1 (was 2.10.3, no longer maintained), and the front page deploy layer requires PROCTOR ^0.11 (locked 0.11.0, was ^0.8 at 0.8.0).
  • Changed: the deploy kit is Squire 0.10.0 (was 0.7.1): release.sh keeps Composer and npm download caches in the app folder and the gate takes SQUIRE_PHP_RUNTIME; the compose file, health.php and .env.squire.example follow the template, and the portable image files are added.
  • Added: a reminder for the Entra client secret's expiry date (OPEN_QUESTIONS.md E-6). Set the optional DRAWBRIDGE_OIDC_CLIENT_SECRET_EXPIRES (YYYY-MM-DD) and config:validate prints the date, the days left and the state (ok; soon at 30 days or fewer; urgent at 7 or fewer; expired) with the rotation steps, /metrics serves drawbridge_oidc_client_secret_days_left (worked out on every scrape, negative once expired), and render writes one drawbridge: warning: line to the container log at start from soon on. Nothing refuses a request; unset changes nothing, and a value that is not a real date is refused at start like any other bad setting.

0.5.0 (2026-11-09)#

  • Docs: the Entra registration guide says a claim that arrives under a long directory extension name can be renamed with {from, as} in oidc.extra_claims (it still said a rename option was not built).
  • Fixed: scripts/a11y.ps1 works on a Windows checkout with CRLF line endings; it strips the carriage returns from the shell command it hands to Docker, which sh rejected with a syntax error.
  • Docs: the front page and docs pages follow the reader's dark mode. The front page had none (it rendered the light sheet even on a dark system); it now gets the docs' after-hours palette, a graphite board with chalk grid, linework in a light tint of the brand green, filled tags in the green itself and gold still gold, with a desk lamp over the hero drawing that flickers on once when motion is allowed. The light page is unchanged, and the a11y gate passes both schemes at 320 and 1280 px.
  • Added: oidc.extra_claims entries can rename a claim with {from, as}, so a long directory-extension claim reaches the app under a short name.
  • Docs: the front page catches up with 0.4.0. The door schedule and its explain box carry the example config's step-up, group and deny rows and print explain's real wording (notes and the deciding rule); the passage outcomes add deny and groups (both 403); the general notes become eighteen from the 55 practices (deny, groups, revoke, top-level sign-out, the event log, the advisory watch); the drafting kit lists revoke; the validate output says 7 path rules; the revision schedule follows OPEN_QUESTIONS.md (bearer tokens and identity on public paths are decided against). The README no longer says one person's sessions cannot be ended (that is drawbridge revoke), and the README art is re-taken (the gatehouse drawing read Rev 0.3; the kit keeps its door cells to the unauthenticated actions). On a 320 px phone the door schedule fits its column: paths break only at a slash and a door's note drops under its key.
  • Added: composer ci now holds the offline half of signing out with third-party cookies blocked (DRAWBRIDGE-25, D50). The browser proofs need the rig, so tests/Unit/SignOutFlowTest.php checks everything in the repository the chain depends on: every app host answers ?logout= itself (uncached, unframeable, never proxied), the session cookie is SameSite=Lax on every host, no directive widens the return or turns on front-channel logout, the rig's provider has none either, the strip hook leaves the endpoint its cookies, the error pages embed nothing, and tools/a11y/signout.mjs still drives the link the guide names.
  • Added: the advisory watch (D37). composer advisories reads the apache2 and mod_auth_openidc floors and the Debian release from the gateway Dockerfile, asks OSV.dev (Debian's security tracker in the OSV format) which advisories still affect each floor, and exits 1 when Debian has a fixed build above one, naming the advisory and the fix; an advisory with no fix yet is listed to watch. It needs the network, so it stays out of composer ci: the new GitLab advisories job runs it from a pipeline schedule or by hand, never on a merge request. FloorWatchTest covers it with canned feed answers.
  • Fixed: the gateway image's mod_auth_openidc floor is 2.4.17-1+deb13u1 (was 2.4.17-1), Debian's fix for CVE-2026-54789, an out-of-bounds read and one-byte write in the state-cookie parser that the advisory watch found on its first run. A mirror or base image that serves the unpatched build now fails the image build instead of shipping it.
  • Changed: CI pins the Preflight components to 0.4.0 (the proctor job clones the full history, so the override-approver check can read git blame).
  • Changed: the deploy layer runs Squire's kit 0.7.1 (was 0.6.0): .squire/php.ini no longer sets the deprecated session.sid_* lines, web requests get a disable_functions list and Apache hardening (.squire/php-web.ini, .squire/apache-hardening.conf), and opcache gets production settings with SQUIRE_OPCACHE_VALIDATE as the one switch.
  • Changed: the front page deploy layer requires HELMET ^1.0 (lock at 1.0.1, was 0.4.0), like the rest of the stack; its shared front controller already runs on HELMET 1.0 in Squire, Sourdough and Pinstripe.
  • Changed: the local a11y scripts run Preflight's own checker (vendored from 0.3.1 and pinned by a test), so they check what CI checks: axe-core 4.14.0, 320 and 1280 px, and the reflow check.
  • Added: CI runs Preflight's a11y component (0.3.1) on site/, every page in light and dark at 320 and 1280 px with the WCAG 1.4.10 reflow check, blocking.
  • Changed: CI pins the Preflight components to 0.3.1 (fixed cache keys, and caches saved even when a job fails; D-072).
  • Changed: CI saves its Composer and npm caches even when a job fails, so a retry after a dropped download fetches only what is missing (D-072).
  • Changed: CI caches Composer and npm downloads under a fixed key, so a lock change downloads only what changed (D-072).
  • Added: an end-to-end test replays a used OIDC callback and proves it no longer signs anyone in (D22).
  • Added: a test pins the gateway image to a non-root user (1001:0, last USER line) on port 8080 (D60).
  • Changed: the PROCTOR job in the GitLab pipeline blocks again (it passes today), and OPEN_QUESTIONS.md marks seven answered or built items as such.
  • Fixed: the docs menu closes with Escape and hands focus back to its button (docs kit synced from Squire).
  • Fixed: the docs kit's copy button no longer covers the first line of code when it says Copied or Failed: over the code it keeps its resting width and shows a check or a cross when the word does not fit (docs kit synced from Squire).
  • Fixed: the front page's version chip shows the full version the docs show (Rev 0.4.0, was Rev 0.4). It carries data-docs-version now, so the docs builder (synced from Squire) rewrites it at every release and composer docs:check fails while it is stale.
  • Changed: the deploy layer requires PROCTOR ^0.8 (locked 0.8.0).

0.4.0 (2026-11-08)#

Added#

  • Added: tools/a11y/signout.mjs, a sign-out check in a real browser engine with third-party cookies blocked (DRAWBRIDGE-25). A Chromium whose engine blocks them signs the rig's test user in through the keycloak profile, shows the gateway session cookie not crossing the site boundary in a cross-site iframe, follows the documented ?logout= chain back to the app host, and replays the old session cookie against a protected path to show it is dead; --skip-signout leaves the session alive, so that run must fail. Run it from tools/a11y with the rig's keycloak profile left up: npm ci, npx playwright install chromium, npm run signout.
  • Added: signing out is proven to work when the browser blocks third-party cookies (DRAWBRIDGE-25). tests/E2E/LogoutTest.php, in the default rig, walks every sign-out hop with a browser that holds only the app host's cookies: each answer is a top-level redirect or the final page, none holds an iframe, a frame, a provider image or a navigating script, the chain ends on the app host and the old session is dead, even with no provider cookie at all. Signing out explains the three hops and why none of them depends on a third-party cookie.
  • Added: the event log (DRAWBRIDGE-18). Besides the access log, the gateway writes one JSON line for each drawbridge.signin, drawbridge.signin_failed, drawbridge.signout, drawbridge.denied and drawbridge.revoked, with v, time, host, path (never the query string), status, user, rule, reason and client, and nothing for an ordinary request. A Lua log hook names the event and cleans every value, so a line is always valid JSON; no cookie, token, header or claim but the subject is ever written. DRAWBRIDGE_EVENT_LOG picks the file (default /dev/stdout). New reference page, Log events. tests/Unit/EventLogFormatTest.php keeps the format and the page in step, and tests/E2E/EventLogTest.php checks every event against the real gateway.
  • Added: drawbridge revoke <subject>... ends every gateway session a person holds now, on every app host, without waiting for it to expire (DRAWBRIDGE-13). It writes <subject> <unix time> to the revocation list (DRAWBRIDGE_REVOCATION_FILE, default /tmp/drawbridge/revoked.txt) under a lock and in one rename, and drops entries older than gateway.session_seconds; --list prints it. The gateway rereads the list at most once a second and refuses a session whose ID token was issued at or before the time: a browser is sent through the ?logout= sign-out (gateway and Entra) back to the app's front door, an api caller gets 401, and nothing is signed. A later sign-in works as before. Several gateway instances must share one mounted file. Signing out now documents the whole chain, and why there is no front-channel (iframe) logout. tests/Unit/RevocationTest.php and tests/E2E/RevocationTest.php cover the list, the command and the gateway.
  • Added: per-path protection gets two more answers (DRAWBRIDGE-33). A deny list of paths that never reach the app (the gateway answers 403 with its own page, signed in or not, and asks nobody to sign in), and default: deny, so only the paths an app lists exist at all. A protected or api rule can name up to 20 groups; a signed-in person who holds none of them in the ID token claim oidc.groups_claim (wsu_roles at WSU) gets 403 and nothing reaches the app. The group check reads the validated ID token itself, whole and case-sensitive, so a client header or a value with a comma in it cannot pass it. The most specific rule decides alone: a child rule replaces its parent's groups and context, and a public path under a deny prefix is open. The config is refused when a rule names groups without oidc.groups_claim, when a public or deny rule names groups or a context, or when a group name has a space or a comma. explain names the groups, the deny and the rule that decided. Each app host now also lets the gateway's own error pages through, whatever its default. Unit tests pin the precedence and the rendered config; tests/E2E/PathRulesTest.php proves it through the rig.

Changed#

  • Changed: the pipeline pins every Preflight CI component to 0.3.0 (preflight@0.3.0); component image inputs are plain image names, since Preflight adds the Dependency Proxy prefix itself.
  • Changed: best practice D36 (flag apps that read raw identity headers) is Documented, not Not yet: PROCTOR's raw-identity-header rule holds it (DRAWBRIDGE-34).
  • Changed: the GitLab pipeline pins the Preflight components to 0.2.0 (was 0.1.4).
  • The front page's deploy layer (deploy/) runs Squire's kit 0.6.0 (was 0.5.0): scripts/release.sh asks PROCTOR's deploy gate for a go or no-go on each release (a report, not a stop, unless SQUIRE_PROCTOR=enforce), and .env.squire.example lists the new setting. The layer's pins move to HELMET ^0.4 (locked 0.4.0) and PROCTOR ^0.7 (locked 0.7.0).
  • Changed: BEST_PRACTICES.md is rewritten in the shape the other stack repos use (DRAWBRIDGE-34). The 14 short rules became 55 numbered practices, D1 to D61, each with a statement, why, sources and exactly one tag (Enforced, Checked, Documented or Not yet), keeping the numbers of the research done before the gateway was built. It covers the new deny rules, group rules, revocation, the event log and sign-out with third-party cookies blocked, and lists the SAML-only items as retired. BestPracticesTest now checks one tag per practice, that every Enforced practice names its tests, that each named method is in the class named, and that the Best practices docs page carries the same list.
  • CI caches Composer downloads per lock file (.composer-cache, keyed on composer.lock and deploy/composer.lock), so a pipeline stops fetching every package from Packagist on every run. Images already come through the Dependency Proxy.
  • Docs: source comments, messages and art titles write Drawbridge as a word, not in capitals; wordmarks keep their display type.

Fixed#

  • Fixed: the rig's keycloak realm sets the post-logout redirect list under post.logout.redirect.uris, the attribute key Keycloak 26.7 reads. The legacy post.logout.redirects key was ignored, so the end-session endpoint validated the return address against the client's redirect URIs only and refused the app host's logout address.
  • Fixed: the pipeline's PROCTOR jobs no longer pass --policy, which PROCTOR 0.7 refuses in CI; PROCTOR checks against the CREED policy it bundles.
  • Fixed: the rig's first-party-only browser now binds each copied cookie to its host. It used to set them with no domain, so they were sent to the provider too, the opposite of a browser that blocks third-party cookies; KeycloakTest::testLogoutWithThirdPartyCookiesBlocked still passes with the stricter copy.
  • Fixed: the front page reads Rev 0.3 and says release 0.3.0 is out (it said release 0.2 was not released yet), and its cast says Sourdough starts all five app shapes, not raw PHP only.
  • Fixed: the README and the upgrading guide pull the 0.3.0 gateway image in their examples, and MAINTAINING.md says the project is released but not deployed.
  • Fixed: the CLI reports the release it ships: php bin/drawbridge --version prints Drawbridge 0.3.0 (it printed DRAWBRIDGE 0.2.0-dev). The front page's revision schedule moves the shared session store (out in 0.2.1) and the live signer counters on /metrics (out in 0.1.1) out of the planned revisions into its account of what is out; the three unbuilt items stay. OPEN_QUESTIONS.md likewise moves the shared session store and graceful passphrase rotation (0.2.1) out of "Not built yet".

0.3.0 (2026-11-07)#

Added#

  • Added: The Proof page records its last run.
  • Added: keys:jwks, which writes the key set file apps verify assertions with: a JWKS of the gateway's ES256 public keys by kid, the current key and the next one. It refuses a private key, another curve, a kid given twice or unusable, and more than 8 keys. SESAME reads the file with gateway.jwks_file (SESAME_GATEWAY_JWKS_FILE).
  • Added: ADR-0001, signing key distribution and rotation (C-7): a key set file of the current and the next key, a yearly rotation, and at least 5 minutes before a retired key leaves the file.
  • Docs: "Rotating the signing key", the runbook for the first key set, a rotation and an emergency; a troubleshooting entry for a gateway that switched to a key the apps never got.

Changed#

  • Changed: the gateway image moves to the stack's image registry: <registry>/enterprise-apps/images/drawbridge-gateway:<tag> instead of this project's own registry (.../drawbridge/gateway:<tag>, which stays readable for the releases already there; they are also copied to the new path with the same digests). gateway-image:publish no longer uses $CI_REGISTRY or $CI_JOB_TOKEN: it logs in with the NOUGAT_REGISTRY_USER and NOUGAT_REGISTRY_TOKEN deploy token at the registry the NOUGAT_REGISTRY project variable names (protected variables, so release tags must be protected), and fails and says why when they are missing. Both image jobs use the dependency proxy only where the GitLab has one, and otherwise pull the Dockerfile's pinned base images straight from Docker Hub. Update docker pull lines to the new path.
  • Changed: The canonical repository is git.wayne.edu (ADR-0021); docs, links and package metadata no longer point at the archived nougat copy.

0.2.2 (2026-11-06)#

Added#

  • Added: a committed accessibility gate (scripts/a11y.sh, scripts/a11y.ps1) runs axe-core (WCAG 2.2 AA) in a real Chromium browser inside Docker against the front page and every docs page, in light and dark mode at two viewport widths; the first run found nothing to fix.

Changed#

  • Changed: the gateway image's vendor build stage takes the refreshed composer:2.11.1 manifest digest (Renovate). The runtime stage and the rendered Apache config are unchanged.

Fixed#

  • Fixed: gateway.session_store: redis with a password-protected Redis works. render never read DRAWBRIDGE_REDIS_PASSWORD (the variable was missing from the list the commands collect), so the gateway rendered no OIDCRedisCachePassword, Redis answered NOAUTH, and every sign-in was a 500. New tests/Unit/EnvTest.php fails if any variable the render options read is not collected.
  • Fixed: the rig's rig/config/drawbridge-redis.yaml is a real config again (the base rig config with session_store: redis and redis_host: redis); the committed file held a stray placeholder line instead, so the redis run could not start the gateway. rig/run.ps1 redis passes both phases: the session survives a graceful reload.
  • Fixed: the default container rig (rig/run.ps1, sh rig/run.sh) starts again under current Docker Compose. Since the Redis session store landed, the gateway service held a hard dependency on the redis service, which only exists under the redis profile, so Compose refused the whole project ("depends on undefined service"). The dependency is now required: false; the redis run still waits for a healthy Redis. The drawbridge was stuck up; it comes down for signed-in people again.

Security#

  • The front-page deploy layer moves to Symfony 7.4.23 (symfony/http-foundation and symfony/yaml advisories, including CVE-2026-118514).

0.2.1 (2026-11-05)#

Added#

  • Added: gateway.session_store: redis (with redis_host, redis_port and the DRAWBRIDGE_REDIS_PASSWORD variable) keeps the gateway sessions in a Redis the operator runs, so they survive a restart and a graceful passphrase rotation and several gateway instances can share them; shm stays the default and renders byte for byte as before. The rig gains a Redis service and tests/E2E/RedisTest.php.

  • Added: DRAWBRIDGE_OIDC_CLIENT_SECRET_FILE, DRAWBRIDGE_OIDC_CRYPTO_PASSPHRASE_FILE and DRAWBRIDGE_OIDC_CRYPTO_PASSPHRASE_PREVIOUS_FILE load those secrets from a file (Docker secrets, Kubernetes volumes); a plain variable still wins, and the trailing newline is stripped.

Changed#

  • Changed: the docs pages wear the front page's drafting look: the same masthead and sheet index (Docs marked current), each page a ruled sheet on the drafting grid with a Big Shoulders Stencil title, commands in the front page's terminal with the gold Copy button in its bar, callouts as tagged drawing notes, the title block as the footer, and a dark mode derived from the terminal skin. Motion only when the reader allows it. The look lives in docs/_header.html and docs/theme/drawbridge.css.

  • Changed: the docs dark mode is no longer a green wallpaper: the board goes graphite under a faint chalk grid, linework and headings take a light tint of the brand green, tags and table header rows keep the brand green itself, and the terminal stays the one deep green surface, as on the front page. The theme now restates the kit's dark colors, which had been handing the page WayneUI's dark green surface. Each sheet carries the front page's enlarged detail bubble with the app icon stamped in, and section rules ink in as they scroll into view (motion only when the reader allows it). Wide tables show a shade at the edge that scrolls, and the footer's full-bleed band no longer leaves the page scrollable sideways.

  • Changed: proxied answers on protected and api paths get Cache-Control: no-store when the app sends none (setifempty); public paths are untouched.

  • Changed: the GitHub mirror is retired (GitHub is only for projects published to Packagist or npm); clone URLs, the README cast strip and the docs mirror list now point at nougat, with git.wayne.edu as the read-only mirror.

Tests#

  • Tests: RenderTest::testProtectedAndApiPathsAddANoStoreDefault and RenderTest::testPublicPathsAddNoCacheHeaderAndSetTheFlag pin the rendered no-store default on login and api blocks and the DRAWBRIDGE_PUBLIC_PATH flag on public ones, and GatewayTest::testProtectedAndApiAnswersCarryNoStoreByDefault and GatewayTest::testPublicAnswersAddNoCacheHeader check the headers end to end on the rig.

  • Tests: GatewayTest::testLoginReturnsOnlyToTheSameHost proves a third-party-initiated login whose target_link_uri names another host (plain, protocol-relative and userinfo tricks) never answers with that host in the Location header or the body, decoded or not, and that a same-host target is not refused as hostile.

  • Tests: SecretFilesShellTest and the RuntimeSecretsTest cases cover the _FILE secrets (newline stripping, precedence, empty and unreadable files).

0.2.0 (2026-11-03)#

  • Fixed: the gateway image jobs pin the Buildah image to the v1.43.5-immutable tag and its manifest list digest, because the previous digest was removed upstream and the tag pipeline failed with "manifest unknown".

Changed#

  • Changed: header mode removed for 1.0. Config validation rejects mode "headers" and "both"; assertion is the only mode. The renderer code stays for a later, gated return. Reason: an unsigned identity header cannot be trusted while app containers may reach each other directly, and the stack's contract is a signed assertion, never a bare header.

Tests#

  • Tests: ConfigLoaderTest::testHeadersModeIsRefused and testBothModeIsRefused pin the config rejection of the removed modes, testAssertionModeStillLoads pins that the default still loads, and SpoofingTest::testAssertionAppsNeverSeeAClientsIdentityHeaders replaces the header-mode E2E check on the rig's second host.

0.1.2 (2026-11-03)#

Added#

  • Added: a docs site (site/docs/) built by the shared docs builder from docs/, checked in composer ci.

  • The gateway image refuses to build when Debian serves apache2 or mod_auth_openidc below the tested floor (apache2 2.4.69-1~deb13u1, mod_auth_openidc 2.4.17-1): the Dockerfile checks the installed versions with dpkg --compare-versions right after the install, and DockerfileFloorTest pins the floor, its position after the install, and the README documentation.

  • Changed: the front-page deploy layer pins HELMET ^0.3, PROCTOR ^0.4 and CREED ^0.1 (lock: HELMET 0.3.0, PROCTOR 0.4.0, CREED 0.1.6).

  • Changed: CI pins Preflight 0.1.4 (GitLab component includes and the GitHub reusable workflow at its tag commit); the deploy layer sets minimum-stability to stable.

  • Docs: README "Three sessions, three clocks" table says how the Entra, gateway and app sessions relate: each lifetime, what ends it, and how to keep the app session from outliving the gateway sign-in (D30).

0.1.1 (2026-11-03)#

Added#

  • Rig: an opt-in keycloak argument (rig/run.sh keycloak, rig/run.ps1 keycloak) starts a pinned Keycloak from a hand-written realm as a second identity provider. It checks the client secret and PKCE, knows only two synthetic users, and refuses unregistered redirect URIs; the Keycloak tests sign one of them in and out through the gateway.
  • A shared file-backed metrics store: the long-running assertion signer and the per-request /metrics endpoint keep their counters in one directory (default /tmp/drawbridge-metrics, moved by DRAWBRIDGE_METRICS_DIR), one JSON file per metric family, written atomically while a per-family lock is held, so a reader always sees a whole file and two writers never lose an increment. When the store cannot be created or written, the signer counts in memory and the endpoint serves build info only.
  • The gateway image serves /metrics itself: it installs php-cgi, and render maps ^/metrics$ to bin/metrics with a virtual-host-level ScriptAliasMatch beside a <Location> that stands outside sign-in and signing. Apache passes no server environment to a CGI child, so a fixup hook hands the child the access rules (DRAWBRIDGE_METRICS_TOKEN, DRAWBRIDGE_METRICS_ALLOW, DRAWBRIDGE_METRICS_DIR) from the request, where the environment is still whole.
  • Rig: the gateway runs with a throwaway metrics token, and the end-to-end tests check every app host answers /metrics to the bearer token (200, text/plain, Cache-Control: no-store) and refuses it otherwise (403).
  • Rig: an opt-in rotation argument (rig/run.sh rotation, rig/run.ps1 rotation) walks a crypto passphrase change through the running gateway: it signs in, re-renders the Apache config with the new passphrase while keeping the old one as mod_auth_openidc's documented previous value, sends Apache a graceful reload, and replays the saved session cookie. It documents that the pinned module accepts the two values but rebuilds its shared-memory session store empty on every reload, so the saved cookie is refused and the browser is sent to sign in again; the same refusal holds once the old passphrase is dropped and after the gateway container is recreated.
  • Tests: the rendered session cookie flags are pinned: OIDCCookieSameSite Lax and OIDCCookieHTTPOnly On hold whether secure cookies are on or off, and OIDCCookieSameSite None never appears.
  • Tests: GatewayTest::testTheSessionCookieIsHttpOnlyAndLaxAtCallback signs in through the rig and reads the session cookie the gateway actually set out of the BrowserKit cookie jar: it is HttpOnly, SameSite=Lax, scoped to path /, and carries no Domain attribute beyond the app host.
  • Tests: BestPracticesTest verifies that every test method and class cited in BEST_PRACTICES.md still exists under tests/, so the document cannot drift from the suite.
  • Tests: the gateway error pages are pinned to WCAG 2.2 AA properties: text contrast of at least 4.5:1 in both the light and dark color schemes, a viewport that does not block zoom, a visible focus outline of at least 2px, and a body text size of at least 16px with headings set in rem or em.
  • Tests: KeycloakTest::testLogoutWithThirdPartyCookiesBlocked signs alice in through the Keycloak rig profile, then strips every identity-provider cookie from the browser's cookie jar (a simulation of a browser that blocks third-party cookies, not a real-browser run) and proves the gateway logout still ends the gateway session with only the app host's cookies left.
  • Tests: RealSesameTest::testAReplayedTokenFails presents one signed assertion twice to one SESAME GatewayDriver instance (through a new optional repeat field in tests/Support/sesame-verify.php) and proves the first presentation passes while the second is refused as a replay.
  • Tests: SpoofingTest::testADuplicatedIdentityHeaderNeverReachesTheApp sends the identity header twice in one raw request (two values, two spellings, and twice beside the email header) and proves no X-Authenticated-* value reaches the echo app, anonymous on a public path and signed in on a protected one.
  • Tests: E2eProvidersTest pins the shape of SpoofingTest::duplicatedIdentityHeaders, so each data set stays one list argument instead of spreading into a string per line.
  • Tests: GatewayTest::testAnApiPathAnswers401ForADeadSession signs in, keeps a copy of the session cookie, ends the session through the logout callback, then replays the dead cookie on an api path with an Accept: application/json header and proves the answer is a bare 401 with no Location header.
  • Docs/Tests: BEST_PRACTICES.md no longer claims that every rule has a test. Each rule now names the tests that prove it, or says plainly that it has none yet, and BestPracticesTest::testEveryRuleNamesItsTestsOrSaysNotTested fails when a rule names neither.
  • Tests: the default catch-all host's hardened headers are pinned: Referrer-Policy: strict-origin-when-cross-origin and Content-Security-Policy: frame-ancestors 'none' stand at host level beside the existing no-store and nosniff, both setifempty so a location that sets its own value keeps it, and the /_drawbridge/up location keeps its own plain set.
  • Tests: the rendered session lifetimes are pinned: OIDCSessionMaxDuration follows gateway.session_seconds (default 28800, 300 to 604800) and OIDCSessionInactivityTimeout follows gateway.session_idle_seconds (default 3600, 60 to 86400), checked with the fixture defaults and with configured values.
  • Tests: SignerMapTest::testTheLogCarriesAReasonCodeAndNoSubjectOrToken proves a refused signing request leaves exactly one reason-code line in the signer's log, with no subject, attribute or token, and SignerMapTest::testAFailureLogsOnlyTheExceptionClass proves a signing failure logs only the exception class, never its message.

Changed#

  • Changed: docs and package metadata name nougat as the canonical repository, with git.wayne.edu and GitHub as read-only mirrors, until git.wayne.edu has CI runners.
  • CI pulls its Docker Hub images through the GitLab Dependency Proxy (the group's CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX), including the base images of the gateway image build, so pipelines no longer hit Docker Hub's anonymous pull limit.
  • Changed: the default catch-all host now answers every response on it (the unknown-host 403 and the error pages included) with Referrer-Policy: strict-origin-when-cross-origin and Content-Security-Policy: frame-ancestors 'none', both setifempty. No HSTS is added because the default host has no known public scheme, and app hosts are unchanged.

Fixed#

  • Fixed: the CI buildah image pin points at the current digest (the old one was re-pushed upstream and no longer resolves).
  • Fixed: DRAWBRIDGE_SESSION_CACHE_ENTRIES refuses a value below 10 or a value that is not a whole number when the config is rendered, instead of casting it and sizing the shared-memory cache with whatever survives.

0.1.0 (2026-11-02)#

The first release is a gateway built on Apache httpd and mod_auth_openidc in front of Microsoft Entra ID over OpenID Connect, with a signed assertion for SESAME's gateway driver.

Added#

  • Per-app config (YAML or PHP array) with exact and prefix path rules, login, api and public protection, and assertion, headers or both delivery. config:validate reports every problem at once.
  • render turns the config into Apache config and a Lua policy; explain says which rule applies; keys:generate makes an ES256 key pair.
  • ES256 assertion signer (typ: drawbridge+jwt, kid, iss, aud, sub, iat, nbf, exp, jti, auth_time, amr) behind Apache's prg: rewrite map. A signing failure gives 503.
  • composer ci: manifest validation, PHPUnit, Pint, PHPStan level 8, composer audit. GitLab and GitHub CI.
  • README.md, BEST_PRACTICES.md, OPEN_QUESTIONS.md, .env.example, MIT licence.
  • README section on getting WSU values from Playbook.
  • Added: agent-ready site (prompt blocks, Markdown twins, llms.txt), from Squire's kit.
  • Gateway error pages: 403, 502, 503 and 504 answer with a small self-contained page (inline CSS, system fonts, no scripts, no external assets, dark-mode aware) served from /_drawbridge/errors/. 401 stays bare for api callers, and the /metrics endpoint keeps its empty-body 403.
  • auth_context on a path rule (c1 to c99): the gateway asks Entra for the context with the claims request parameter and requires it in the ID token's acrs array, sending a signed-in visitor without it back to step up (api paths answer 401).
  • Rig tests for step-up, forged callbacks and forged OIDC_* headers.
  • GitLab pipeline builds the gateway image with Buildah (unprivileged, pinned by tag and digest) on every merge request and the default branch, and publishes it to the project's container registry when a tag is pushed (gateway:<tag>, no latest). The image carries OCI labels (source, revision, version, licenses).
  • An off-by-default Prometheus /metrics endpoint (bin/metrics), on when DRAWBRIDGE_METRICS_TOKEN (bearer token) or DRAWBRIDGE_METRICS_ALLOW (client IPs/CIDRs) is set; a disabled or misconfigured endpoint answers 404 and an unauthorized request 403. Reports drawbridge_build_info; the assertion-signing counters (drawbridge_signing_requests_total, drawbridge_assertions_signed_total, drawbridge_assertion_errors_total{reason}) are kept in the signer for in-process use and are not registered on the endpoint until a shared store lets it see the signer's counters; labels carry no identity, claim, or token.
  • Response headers: every proxied answer gets X-Content-Type-Options: nosniff and Referrer-Policy: strict-origin-when-cross-origin, plus Strict-Transport-Security: max-age=31536000 when the public scheme is https, each with setifempty so an app that sends its own header through HELMET keeps it. The /_drawbridge/ locations the gateway answers itself get Cache-Control: no-store and Content-Security-Policy: frame-ancestors 'none', and the default host answers its 403 and error pages with no-store too. HSTS carries no includeSubDomains and no preload: the gateway serves many hosts and must not decide that for them.
  • Docs: ENTRA_TEST.md (first real Entra test checklist) and a "Try it without Entra" README section.

Changed#

  • mod_auth_openidc (Debian package, pinned like the rest of the image). Authorization code flow with PKCE, one client for every app host, the redirect URI at /_drawbridge/oidc/callback on each host, sessions in an encrypted shared-memory cache with a passphrase per host.
  • Config: the oidc block (issuer, metadata_url, client_id, client_secret_env, user_claim, attribute_claims, extra_claims, amr_map). The issuer must be https (http only for a .test host). config:validate and explain print the fields, never the secret.
  • The signer reads the validated ID token: sub from the user claim (preferred_username by default, configurable, for example to accessid), auth_time, amr (Entra values through the default map), acrs, the attribute claims and any extra_claims such as wsuRoles. An ID token from another issuer is not signed. The signer's input line is v2.
  • The guard strips OIDC_CLAIM_*, OIDC_access_token and the module's other token and claim names, and removes every header under an owned prefix whatever follows it.
  • render refuses to write anything when the client secret or crypto passphrase is missing or unsafe to substitute, so Apache never starts with a literal ${...} for a secret.
  • Rig: mock-oauth2-server 6.1.3 as the test IdP.
  • Config: the example and rig set oidc.user_claim: accessid, the AccessID the Entra app registration sends (transformed from the user principal name with ExtractMailPrefix); preferred_username works for a tenant that does not send accessid. The example also lists wsuRoles in extra_claims, a mapped claim that needs no custom signing key. The gatehouse takes names as the AccessID, because even a drawbridge only lifts for barges it knows.
  • Coding standard: the PHPStan settings include Pinstripe's raw PHP cut (waynestate/pinstripe is a dev dependency, and phpstan.neon keeps only this repository's paths and PHP version range). Two findings from the preset's deprecation and @var checks are fixed: the signer builds JWTs with Builder::new() instead of the deprecated lcobucci/jwt constructor, and the metrics allow-list keeps its runtime entry validation in a dedicated helper.
  • Changed: project names written as words except acronyms.
  • Changed: examples, docs and tests use wsu_roles, the roles claim name Entra sends (the directory attribute stays user.wsuRoles).

Fixed#

  • Fixed: stale capability claims in the site and README.