docs(identity): per-request front-end origin for auth e-mail links#232
Open
marcelo-maciel wants to merge 2 commits into
Open
docs(identity): per-request front-end origin for auth e-mail links#232marcelo-maciel wants to merge 2 commits into
marcelo-maciel wants to merge 2 commits into
Conversation
Documents that CorsOptions.AllowedOrigins now doubles as the allowlist the Identity module validates the request Origin against to build password-reset and e-mail-confirmation links (per PR fullstackhero/dotnet-starter-kit#1323): - security/cors-and-headers: new section + common-mistake note - security/production-checklist: AllowedOrigins gates the auth e-mail flows - modules/identity: callout on where reset/confirmation links point - changelog: 2026-07-02 entry
Update the origin docs to the reworked #1323 model: link resolution moved off CorsOptions onto a dedicated FrontendOptions (AllowedOrigins + DefaultOrigin). - cors-and-headers: rewrite the front-end-origin section — decoupled from CORS, self-service vs operator-driven flows, no-header fallback to DefaultOrigin, forged origin -> 400, startup validation, component-wise matching. - modules/identity: callout reflects FrontendOptions + recipient-app targeting for register/resend. - production-checklist: FrontendOptions is a separate required setting whose startup validation fails the boot until configured. - changelog: describe the FrontendOptions model and the updated deploy action.
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
1 participant
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.
Documents the behaviour introduced by dotnet-starter-kit#1323: password-reset and e-mail-confirmation links now resolve to the front-end that made the request, via the request
Originheader validated againstCorsOptions.AllowedOrigins.Changes:
AllowedOrigins' second role (link allowlist + security boundary against a forgedOrigin), plus a common-mistake note.AllowedOriginsgates the reset/confirmation e-mail flows, not just CORS./confirm-emailpage.Pairs with code PR #1323; ideally merges alongside or just after it. (Did not run
astro buildlocally — nonode_modulesin my checkout — but the changes are prose plus one<Callout>matching existing usage, no new imports.)