Skip to content

Authorization Server Template

Repository: ConnectSoft.AuthorizationServerTemplate
Layer: 3 (extends ConnectSoft.BaseTemplate via base-template/ submodule)
Stack: OpenIddict for OAuth 2.x and OpenID Connect

Purpose

This template scaffolds an authorization server capable of token issuance (access / refresh / identity tokens per configured flows), client registration, consent (where applicable), and integration with the user store provided by Identity Backend. It is the trust anchor for many ConnectSoft SaaS deployments alongside the API Gateway.

Architectural boundaries

Component Responsibility
Authorization Server (this template) OAuth/OIDC protocols, client credentials, signing keys, token formats
Identity Backend User profiles, credentials, roles, often the user store
API Gateway Validates tokens at perimeter; may propagate claims

Typical flow: client obtains tokens from Authorization Server; resource servers (microservices) validate JWTs (issuer, audience, signing keys); Identity remains authoritative for user state.

Composition with Base Template

  • Uses the same prefixed solution layout and three-layer DI pattern as other web extended templates.
  • HangFire, SQL, and other optional stacks must follow Extended template configuration alignment — known hotspot: Acceptance vs Application catalog names and HangFire connection string keys must stay aligned across environments.

Documentation map

Section Purpose
Getting Started Install, run
Parameters Scaffold flags
Solution structure Projects
Architecture OIDC server boundaries
Features Flows, clients, tokens
Configuration OpenIddict, signing
Authentication Token issuance surface
Resiliency Edge stability
Testing Tests
Development Extend server
Use cases OIDC scenarios
Runbook Ops

Product roadmap

Long-term goals and how they relate to commercially marketed OpenIddict companion products (benchmark only) are summarized in repo ConnectSoft.AuthorizationServerTemplate — Docs/OpenIddict-Ecosystem-Roadmap.md.

Alignment hotspots

Keep Acceptance and Application appsettings catalog names and HangFire connection string keys aligned — see Extended template configuration alignment.