Table of Contents

Getting started

This page gets you from nothing to a working multi-tenant app with team management, API-key authentication, and the Blazor UI components. For the full breakdown of every option — and a step-by-step alternative to the single call below — see the Implementation guide.

Install

dotnet add package Tharga.Team.Blazor
dotnet add package Tharga.Team.Service
dotnet add package Tharga.Team.MongoDB
  • Tharga.Team.Blazor — the UI components and authentication.
  • Tharga.Team.Service — server-side API-key auth, Swagger, audit.
  • Tharga.Team.MongoDB — persistence. Swap this for your own ITeamService / IUserService backend if you don't use MongoDB.

Register

builder.AddThargaPlatform(o =>
{
    o.Blazor.Title = "My App";
    o.Blazor.RegisterTeamService<MyTeamService, MyUserService>();
});

var app = builder.Build();
app.UseThargaPlatform();

AddThargaPlatform registers, with sensible defaults:

Concern What you get
Authentication Azure AD + OIDC login/logout endpoints and claims augmentation.
API keys Header-based API-key authentication and management/administration services.
Blazor UI TeamSelector, TeamComponent, ApiKeyView, SystemApiKeyView, UsersView, LoginDisplay, AuditLogView, and more.
Controllers API controllers + Swagger integration.

Configure authentication

AddThargaPlatform expects an AzureAd section in appsettings.json:

{
  "AzureAd": {
    "Authority": "https://<tenant>.ciamlogin.com/<domain>",
    "ClientId": "<client-id>",
    "TenantId": "<tenant-id>",
    "CallbackPath": "/signin-oidc"
  }
}

Implement the backend types

RegisterTeamService<MyTeamService, MyUserService>() needs your two service implementations. With the MongoDB package these derive from the provided base classes and entity types — see Step 4: Team Management for the entities, UserService, and TeamService.

Next

Edit this page