Skip to content

Authorization Server Template — Parameters

Discovery

The shortName and exact symbol set ship with the installer published from ConnectSoft.AuthorizationServerTemplate. After install:

dotnet new <shortName> -h

Use the shortName printed in that repo’s .template.config/template.json or release notes (registry may show “see repo”).

Inherited from Base Template

Like other Layer 3 web templates, the Authorization Server reuses the Base symbol surface for:

  • Ports, Docker, health, OpenTelemetry, feature flags, distributed cache, optional persistence / migrations toggles, messaging / actors when enabled, etc.

See Base Template — Parameters for the kernel reference tables.

Authorization-server–specific areas

Engineers should confirm via -h and generated docs:

Area Typical focus
OpenIddict Stores, certificate / signing configuration hooks
Client / consent Scaffold options that include sample clients or empty stores
HangFire / background jobs If enabled, keys must follow configuration alignment
Database catalog names Known hotspot: consistency between layers—see overview