Skip to content

Identity Backend Template

Repository: ConnectSoft.IdentityTemplate
Short name: connectsoft-identity
Layer: 3 (extends ConnectSoft.BaseTemplate via base-template/ submodule)

Purpose

The Identity Backend template generates a user directory microservice: account lifecycle, credentials (where applicable), ASP.NET Core Identity stores, roles, claims, profile data, MFA (e.g. TOTP / recovery codes patterns when enabled), and APIs consumed by other services. Per repo description, it targets security-first, Clean Architecture, and DDD boundaries suitable for multi-tenant SaaS.

It does not replace a full OAuth2/OIDC authorization server—token issuance, clients, and consent flows normally live in Authorization Server Template (OpenIddict).

Architectural boundaries

Concern Identity Backend Authorization Server
User CRUD, passwords, lockout Primary No
Session / cookie login for interactive flows Often here Delegates / trusts as designed
OAuth2/OIDC token endpoint, client credentials Integrates Primary
JWKS, signing keys for tokens Consumes / trusts Primary

Composition with Base Template

  • Submodule base-template/ points at ConnectSoft.BaseTemplate.
  • ConnectSoft.IdentityTemplate.Application (and related) replaces or forks the Base Application host pattern while reusing MicroserviceRegistrationBase concepts via template-specific registration.
  • Persistence (users, claims) uses the same *Model layout as other Layer 3 services.

Platform fit

  • API Gateway validates tokens and may call Identity for introspection or user APIs depending on design.
  • Templates registry lists this template as a structural reference for Layer 3 layout.

Documentation map

Section Purpose
Getting Started Install, run
Parameters dotnet new
Solution structure Projects
Architecture Identity + DDD
Features Users, roles, MFA
Configuration Stores, lockout
Authentication Login, cookies, consumed tokens
Resiliency Rate limits, idempotency
Testing Tests
Development Extend registration
Use cases Scenarios
Runbook Deploy