Skip to content

Authentication

The template has a top-level .template.config/template.json with short name connectsoft-blazor-mfe and 18 symbols.

Authentication behavior is template-specific and must be confirmed from the current source, appsettings, and package references.

Current Documentation Rule

  • If auth packages, handlers, policies, or OIDC/OAuth settings exist in the repo, document the exact files and options.
  • If they do not exist, this page intentionally remains a not-present statement for this template.

Verified: no built-in Shell authentication by default

src/Shell.BlazorServer/Program.cs calls no UseAuthentication()/UseAuthorization() and registers no authentication scheme. Both sample MFE registration extensions (AddIdentityAdminMfe, AddIdentitySelfServiceMfe in src/Mfe.Identity.*.Blazor/Extensions/ServiceCollectionExtensions.cs) explicitly document that they register neither authentication schemes nor authorization policies, and that "the host owns authentication." The sample pages render mock data with no real identity backing.

The composition convention documented in the template's own docs/Architecture.md is that each MFE registers its own authorization policies inside its own Add{X}Mfe extension — the Shell is only responsible for calling Add{X}Mfe(...) once per composed MFE, not for owning MFE-specific policies. The two current sample MFEs don't yet exercise this convention with real policies; a consuming team wiring real authentication should follow that pattern rather than centralizing policies in the Shell.

Review Solution structure, Configuration, and repo source before changing this page.