👁 Image
OutWit.Identity.Blazor 2.0.7

OutWit.Identity.Blazor

Blazor WebAssembly auth-side bits for apps integrated with WitIdentity.

This package sits on top of the generic OutWit.Shared.Blazor.Shell admin shell and adds the WitIdentity-specific parts: OIDC login UI, tenant manifest types, and a thin shell-layout wrapper that pre-fills branding from /branding.json.

Renamed from OutWit.Identity.Shared in 2.0. The generic shell pieces (AppShellLayout, theme, M3 CSS, AppNotFound, DisplayUtils, LoginMenuItem) now live in OutWit.Shared.Blazor.Shell so non-Identity products can use them without pulling WitIdentity in.

Contents

• IdentityShellLayout — thin wrapper around the generic AppShellLayout that hydrates Title, Header, LogoUrl… from the injected BrandingOptions and slots in <LoginDisplay /> + <AppShellFooter />. Use this from your MainLayout.razor and you only have to supply navigation items.
• AppRoot — root component with CascadingAuthenticationState, Router, and AuthorizeRouteView.
• LoginDisplay — login / logout button with user avatar + dropdown menu populated from LoginDisplayOptions.MenuItems (the LoginMenuItem record itself lives in OutWit.Shared.Blazor.Shell.Model).
• LoginRedirect — sends unauthorised users through the OIDC login flow.
• AppShellFooter — pinned bottom-right server version + environment badge.
• Branding namespace — BrandingOptions, IOidcClientSettings, OidcClientSettings, SystemInfo, TenantManifest (the wire types that match the server's GET /branding.json response).
• CSS at _content/OutWit.Identity.Blazor/css/ — m3-auth.css (login / change-password page styling) and app-shell-footer.css (version badge).

Installation

dotnet add package OutWit.Identity.Blazor

This transitively brings in OutWit.Shared.Blazor.Shell, MudBlazor, and the OIDC authentication libraries.

Usage

In your Blazor WASM Program.cs:

// Fetch the tenant manifest (branding + OIDC client config + server version)
// from the WitIdentity host. Registers BrandingOptions and IOidcClientSettings
// as singletons available via DI throughout the app.
var manifest = await builder.Services.AddIdentityShellTenant(builder.HostEnvironment.BaseAddress);

// Wire up OIDC authentication using values from the manifest. Pass
// `fallbackAuthority` for self-hosted scenarios where the manifest's
// Authority is empty (the identity server itself loading its admin UI).
builder.Services.AddIdentityShellAuth(manifest.Oidc);

// MudBlazor services + login menu.
builder.Services.AddIdentityShellServices(options =>
{
 options.MenuItems.Add(new LoginMenuItem("Home", "/", Icons.Material.Outlined.Home));
});

In index.html:

<link rel="stylesheet" href="_content/OutWit.Shared.Blazor.Shell/css/m3-tokens.css" />
<link rel="stylesheet" href="_content/OutWit.Shared.Blazor.Shell/css/m3-appbar.css" />
<link rel="stylesheet" href="_content/OutWit.Shared.Blazor.Shell/css/m3-nav.css" />
<link rel="stylesheet" href="_content/OutWit.Shared.Blazor.Shell/css/shell.css" />

<link rel="stylesheet" href="_content/OutWit.Identity.Blazor/css/m3-auth.css" />
<link rel="stylesheet" href="_content/OutWit.Identity.Blazor/css/app-shell-footer.css" />

<link rel="stylesheet" href="_content/MudBlazor.FontIcons.MaterialSymbols/css/font.min.css" />

In MainLayout.razor:

@inherits LayoutComponentBase

<IdentityShellLayout>
 <NavigationItems>
 <MudNavLink Href="/" Icon="@Icons.Material.Outlined.Dashboard">Home</MudNavLink>
 </NavigationItems>
 <ChildContent>@Body</ChildContent>
</IdentityShellLayout>

The WitIdentity server publishes the manifest at GET /branding.json (anonymous, Cache-Control: no-cache, must-revalidate). The shape matches the TenantManifest class in this package, so consuming apps deserialise straight into it.

Built with MudBlazor.