AnointedAutomation.SSO.UI 1.0.1

dotnet add package AnointedAutomation.SSO.UI --version 1.0.1
                    
NuGet\Install-Package AnointedAutomation.SSO.UI -Version 1.0.1
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="AnointedAutomation.SSO.UI" Version="1.0.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="AnointedAutomation.SSO.UI" Version="1.0.1" />
                    
Directory.Packages.props
<PackageReference Include="AnointedAutomation.SSO.UI" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add AnointedAutomation.SSO.UI --version 1.0.1
                    
#r "nuget: AnointedAutomation.SSO.UI, 1.0.1"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package AnointedAutomation.SSO.UI@1.0.1
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=AnointedAutomation.SSO.UI&version=1.0.1
                    
Install as a Cake Addin
#tool nuget:?package=AnointedAutomation.SSO.UI&version=1.0.1
                    
Install as a Cake Tool

AnointedAutomation.SSO.UI

Jesus is King ✝️

The ASP.NET Core front end for "Sign in with Anointed Automation": brand-styled, accessible sign-in and sign-out buttons for Razor Pages / MVC (Tag Helpers) and Blazor (Blazor Server, or a Blazor Web App with static SSR or interactive server rendering), plus MapAnointedAutomationAuth() minimal API routes.

It sits on top of AnointedAutomation.SSO, which does the OpenID Connect work. The design is a backend for frontend (BFF): the browser only ever holds your own session cookie. No ID, access or refresh token is sent to the browser, and the user-info route returns claims, never tokens. The buttons look the same as the React button.

Server rendering only. Do not use this in Blazor WebAssembly: there is no client secret in the browser. A WebAssembly app calls the user and sign-out routes of its ASP.NET Core host instead.

Starting fresh? dotnet new install AnointedAutomation.Templates, then dotnet new anointed-razor or dotnet new anointed-blazor (templates).

Install

dotnet add package AnointedAutomation.SSO.UI

Wire it up (Program.cs)

using AnointedAutomation.SSO;
using AnointedAutomation.SSO.UI;
using Microsoft.AspNetCore.Authentication.Cookies;

builder.Services
    .AddAuthentication(options =>
    {
        options.DefaultScheme = CookieAuthenticationDefaults.AuthenticationScheme;
        options.DefaultChallengeScheme = AnointedAutomationDefaults.AuthenticationScheme;
    })
    .AddCookie()
    .AddAnointedAutomation(options =>
    {
        options.ClientId = builder.Configuration["Anointed:ClientId"];         // required, no default
        options.ClientSecret = builder.Configuration["Anointed:ClientSecret"]; // server only
        options.CallbackPath = "/auth/anointed/callback";
    });
builder.Services.AddRazorPages(); // or AddRazorComponents(); both register antiforgery

WebApplication app = builder.Build();
app.UseAuthentication();
app.UseAuthorization();
app.UseAntiforgery();

app.MapAnointedAutomationAuth("/auth/anointed");

AddAnointedAutomation throws at startup when the client id or secret is missing.

Routes

Route What it does
GET /auth/anointed/start?returnTo=/account Starts sign-in. returnTo must be a same-site path (/account); anything else lands on /.
POST /auth/anointed/sign-out Ends the local session and, when the provider publishes an end_session_endpoint, signs out at Anointed Automation too (RP-initiated logout). Needs a form antiforgery token (the buttons add it) or, from script, the header X-Anointed-CSRF: 1. A form gets a redirect to the provider; a script gets 200 with {"redirect":"https://..."} to navigate to (or 204 when only the local session ended).
GET /auth/anointed/user {"isAuthenticated":true,"sub":"...","email":"...","name":null,"preferredUsername":null,"picture":null} for single page apps. Never a token. Cache-Control: no-store.

Options (app.MapAnointedAutomationAuth("/auth/anointed", o => { ... })): ChallengeScheme (default Anointed), CookieScheme (default Cookies), ReturnToParam (default returnTo), DefaultReturnPath (default /), SignOutOfProvider (default true). The call returns the route group so you can add rate limiting or other conventions.

Sign-out clears the local cookie, then (when ChallengeScheme is the OpenID Connect scheme from AddAnointedAutomation and discovery lists end_session_endpoint) signs out the Anointed scheme so the browser ends the Anointed Automation session and comes back to returnTo. Set SignOutOfProvider = false to end the local session only. To react to a sign-out made at Anointed Automation, map the back-channel logout endpoint from AnointedAutomation.SSO.

Razor Pages / MVC

_ViewImports.cshtml:

@addTagHelper *, AnointedAutomation.SSO.UI
@if (User.Identity.IsAuthenticated)
{
    <anointed-sign-out action="/auth/anointed/sign-out" />
}
else
{
    <anointed-sign-in start-url="/auth/anointed/start" return-to="/account" />
}

Attributes: start-url (required) / action (required), return-to, return-to-param, label. Pass class to drop the built-in inline look and style the button yourself.

Blazor

_Imports.razor: @using AnointedAutomation.SSO.UI.Components

<AuthorizeView>
    <Authorized><AnointedSignOutButton Action="/auth/anointed/sign-out" /></Authorized>
    <NotAuthorized><AnointedSignInButton StartUrl="/auth/anointed/start" ReturnTo="/account" /></NotAuthorized>
</AuthorizeView>

The sign-in button is a real link marked data-enhance-nav="false" so Blazor does a full page load to the start route. The sign-out button is a plain POST form with <AntiforgeryToken />, so it works in static SSR and in interactive server mode. Parameters: StartUrl / Action (required), ReturnTo, ReturnToParam, Label, Class, plus any extra attributes.

Accessibility

Real <a> and <button> elements, visible text label, decorative logo with alt="" and aria-hidden="true", white on #1f2a44 (contrast well above WCAG AA).

License

MIT.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.0.1 85 10/26/2026
1.0.0 92 10/24/2026