Step-up sign-in#
This page explains how a path rule asks for an Entra authentication context on top of a sign-in, and what happens when the visitor's token does not carry it.
Naming the context#
A path rule can name an Entra authentication context (c1 to c99):
protected:
- /admin/
- path: /admin/payroll/
auth_context: c1
On that path the gateway asks Entra for the context with the OpenID Connect claims request parameter
({"id_token":{"acrs":{"essential":true,"value":"c1"}}}) and lets the request through only when the ID token's
acrs array lists c1.
When the context is missing#
A visitor already signed in without it is sent back to Entra to step up (mod_auth_openidc answers with a short page
that forwards the browser); an api path answers 401.
What the context demands#
What c1 actually demands (MFA, a compliant device, a fresh sign-in) is a Conditional Access policy in Entra, not
Drawbridge config.
The check is made twice#
The check is made twice: by mod_auth_openidc's Require claim acrs:c1, and again by the gateway's own stamp step.
Check it#
Sign in without the context first, then request the step-up path: the visitor should be sent back to Entra and come
back with the context listed in acrs. That is row E-5 of the first real Entra test in ENTRA_TEST.md.