# Drawbridge > Drawbridge is the sign-in gateway we're building for Citadel, Wayne State's container platform: Apache with mod_auth_openidc as one OpenID Connect client for Microsoft Entra ID. It drops any identity header a visitor sends and passes the app a 60-second ES256-signed assertion that SESAME checks. It isn't in front of any apps yet. **Comes down for signed-in people.** Checks: `composer ci` (the same command runs in the GitLab pipeline and in the GitHub Actions workflow kept in `.github/`). The container rig has its own script, see "Run the checks". > The one way into the Citadel. It only comes down for people who signed in. Drawbridge is the sign-in gateway for the apps on Citadel, Wayne State's container platform. It is Apache with mod_auth_openidc, set up as one OpenID Connect client for Microsoft Entra ID. It is not live yet: its home will be `auth.apps.wayne.edu`, in front of every app on the platform, once the Citadel routing for it exists. The latest release, 0.6.2, is tagged. It builds the gateway image, which will run as a service on Citadel. As a reverse proxy it checks that the visitor has a session, drops any identity header the visitor sent, and passes the app a short-lived signed assertion that SESAME's `gateway` driver verifies. Which paths need a login, and which need an Entra authentication context on top, is declared per app in a config file. Nothing else decides it. Why a moat and not a lock on every door: each app doing its own OpenID Connect is another chance to get a nonce, a state check or a token signature wrong. We'd rather get that right once, in a maintained module (mod_auth_openidc). Each app then checks one small signed token. Every page below is Markdown. The HTML pages send the same Markdown to a client that asks for `text/markdown`. Written by Squire's agent-ready kit from the README and the pages; do not edit. ## Pages - [Drawbridge: Comes down for signed-in people](https://drawbridge.apps.wayne.edu/index.md): Drawbridge is the sign-in gateway we're building for Citadel, Wayne State's container platform: Apache with mod_auth_openidc as one OpenID Connect client for Microsoft Entra ID. It drops any identity header a visitor sends and passes the app a 60-second ES256-signed assertion that SESAME checks. It isn't in front of any apps yet. - [Changelog | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/changelog.md): All notable changes to this project. - [Contributing | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/contributing.md): How to contribute to Drawbridge, including where the canonical repository lives and how to open issues and merge requests on it. - [First deployment | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/deploying/first-deployment.md): The first run of a released gateway image on a pre-production host with the trial kit: the files to make, the compose and docker run shapes, the health check, the smoke check, logs, metrics, a rollback and the teardown. - [Getting the image | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.md): How the pipeline builds and publishes the gateway image, and how to pull and verify a pinned release by its digest. - [Releasing | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/deploying/releasing.md): How to tag and release Drawbridge and publish its gateway image, and where the build, test and release steps are documented. - [Error pages and response headers | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/error-pages-and-headers.md): The small self-contained error pages the gateway answers itself, and the response headers it adds to proxied answers without overriding the app's own. - [How it works | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/how-it-works.md): How a request takes the same passage through the gatehouse: the guard strips identity headers, the OpenID Connect client checks the session, and the signer hands the app a short-lived signed assertion. - [Metrics | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/metrics.md): How to turn on and protect the Prometheus metrics endpoint, and the counters it serves about signing requests and assertions. - [Protecting paths | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/protecting-paths.md): How each app declares its public, protected, api and deny paths and its groups in one config file, how the most specific rule wins with no wildcards, and how a deny default keeps unlisted paths closed. - [Quick start | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/quick-start.md): A quick start that copies the example config and environment file, validates them, builds the gateway image, and runs the rig against a mock provider. - [Register Drawbridge in Entra ID | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/register-in-entra.md): How to register Drawbridge as one app registration in Entra ID, covering redirect URIs, the client secret, token claims and authentication contexts. - [Rotating the signing key | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/rotating-the-signing-key.md): How apps get Drawbridge's public keys (a JWKS file of the current and the next key) and how to rotate the signing key without locking anyone out, including the emergency steps. - [Sessions and lifetimes | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/sessions.md): The three sessions a signed-in visitor holds at once, each with its own lifetime and owner, and what ends each one. - [Signing out | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/signing-out.md): How an app links to the logout callback so the gateway ends its session for that host and sends the browser through Entra's sign-out, and how to end every session a person holds with drawbridge revoke. - [Step-up sign-in | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/step-up.md): How a path rule names an Entra authentication context and sends a signed-in visitor back to step up when the context is missing from the token. - [Try it without Entra | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/try-without-entra.md): How to run the container rig, which signs synthetic users in against a mock OpenID Connect provider so nothing in the trial reaches Entra. - [Using the assertion in an app | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/using-the-assertion.md): How to point SESAME's gateway driver at Drawbridge so the app checks the signed assertion instead of parsing the token itself. - [WSU values (Playbook) | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/guides/wsu-values.md): Where to look up Wayne State's shared values in Playbook and copy them into the config and environment file, since Drawbridge never reads Playbook in code. - [Overview | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/index.md): An overview of Drawbridge, the sign-in gateway for the apps on Citadel and the one way in that comes down only for people who signed in. - [Install | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/install.md): How to clone Drawbridge and get it running with Docker, the only thing you need, with separate commands for Windows and for Linux and macOS. - [Best practices | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/reference/best-practices.md): The practices the gateway holds itself to, each with its sources, one tag and the tests that hold it, from BEST_PRACTICES.md. - [Commands | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/reference/commands.md): Every drawbridge command and what it does: config:validate, explain, render, revoke, smoke, keys:generate, keys:jwks and signer:map. - [Configuration | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/reference/configuration.md): The full configuration reference: the oidc block, the gateway block, and each app's id, host, upstream, mode and path rules. - [Log events | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/reference/log-events.md): The JSON event log the gateway writes for every sign-in, failed sign-in, sign-out, refusal and revoked session, field by field, and what it never contains. - [Proof | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/reference/proof.md): The tests that prove the gateway keeps its rules: the unit suite, the container rig and the end-to-end runs, and how to run them. - [Troubleshooting | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/troubleshooting.md): What to check when sign-in, signing or the rig misbehaves, and how to read the gateway's plain answers and reason codes. - [Upgrading | DRAWBRIDGE docs](https://drawbridge.apps.wayne.edu/docs/upgrading.md): How to move Drawbridge forward to a new PHP version, module version or stack release without breaking the gateway. ## Prompts - [Get started with Drawbridge](https://drawbridge.apps.wayne.edu/#prompt-get-started): Clone, validate the example config, ask explain about three doors, and run the rig against a mock provider. Nothing reaches Entra. The prompt itself is in https://drawbridge.apps.wayne.edu/index.md. - [A Laravel app behind Drawbridge](https://drawbridge.apps.wayne.edu/#prompt-laravel): Its door schedule for the gate, and SESAME's gateway driver checking the signed assertion on the way in. The prompt itself is in https://drawbridge.apps.wayne.edu/index.md. - [A raw PHP app behind Drawbridge](https://drawbridge.apps.wayne.edu/#prompt-raw-php): The same door schedule, and SESAME's gateway driver built by hand, with the check placed before any output. The prompt itself is in https://drawbridge.apps.wayne.edu/index.md. ## Source - [README](https://git.wayne.edu/enterprise-apps/drawbridge/blob/HEAD/README.md): the project's README, with install, commands and checks - [Everything in one file](https://drawbridge.apps.wayne.edu/llms-full.txt): the README and every page above, as one Markdown file ## Optional - [ADVISOR](https://advisor.apps.wayne.edu/llms.txt): the stack's MCP server: read-only tools that answer from CREED's policy and the parts' docs instead of from memory - [WELD](https://weld.apps.wayne.edu/llms.txt): the Wayne State application stack: every part, and the reference app