docs(deploy): Microsoft Entra ID walkthrough (oauth2-proxy header mode)#2139
Open
dosenr wants to merge 1 commit into
Open
docs(deploy): Microsoft Entra ID walkthrough (oauth2-proxy header mode)#2139dosenr wants to merge 1 commit into
dosenr wants to merge 1 commit into
Conversation
…e) + native-OIDC caveat Entra ID tokens do not carry email_verified by default, so native OIDC sign-in is hard-rejected; the docs listed Entra under Generic OIDC with no working path. Adds the oauth2-proxy header-mode walkthrough (v2.0 tenant issuer, the preferred_username email-claim quirk, guest-UPN caveat, header-strip behavior) and a note in the OIDC section pointing to it. Signed-off-by: Robert Dosen <robert.dosen@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue
N/A (docs addition; no tracking issue exists for Entra deploy docs)
Summary
The Generic OIDC section lists Entra ID as a supported issuer, but the server hard-rejects OIDC sign-ins without a verified email claim and Entra ID tokens do not include
email_verifiedby default, so native OIDC sign-in with Entra fails. This adds a note stating that in the OIDC section, and documents the working path as a walkthrough in the Header-proxy section: oauth2-proxy with Entra ID.The walkthrough covers the app registration, the v2.0 tenant issuer URL, and the non-obvious
OAUTH2_PROXY_OIDC_EMAIL_CLAIM=preferred_usernamesetting (Entra frequently omits theemailclaim; guest accounts carry a non-email UPN, noted). It also gives oauth2-proxy its first config example in these docs; it is the first proxy the header-mode section names.Test Plan
Docs only; no code paths changed. The configuration is the one running in our production deployment (oauth2-proxy 7.x, Entra ID single tenant, header mode).
Demo
N/A (documentation).
Type of change
Changelog
Added a Microsoft Entra ID deploy walkthrough (oauth2-proxy header mode).