Identity Backend Template — Parameters¶
Discovery¶
Install the published package, then:
Authoritative metadata: .template.config/template.json in ConnectSoft.IdentityTemplate. Layer 3 repos may merge or extend Base template JSON; treat -h output for your installed version as the live contract.
Inherited from Base Template¶
Identity is a web extended template on ConnectSoft.BaseTemplate. Most cross-cutting symbols (HTTP/HTTPS ports, Docker, Logging, OpenTelemetry / collector stacks, HealthCheck / Health Checks UI, distributed cache, feature flags, persistence model toggles, UseRestApi / UseGrpc, UseMassTransit, UseOrleans, HangFire, AI / vector optional stacks, etc.) are defined in the Base template and flow into the composed installer.
See Base Template — Parameters for the full kernel catalog with descriptions.
Identity-specific considerations¶
While symbol names are versioned in repo metadata, engineers typically verify:
| Area | Notes |
|---|---|
| Host / ports | Mirrors Base patterns for Kestrel / launchSettings |
| Persistence | User store, tokens (if persisted), EF or NHibernate per template generation (follow generated README) |
| Docker / k8s | Optional compose and manifests when Docker (or equivalent) is true |
| Observability | Same OTel / App Insights toggles as Base when included in merge |
After scaffold¶
- Run README / Docs in the generated repo for connection strings and first-time migrations.
- Align Acceptance vs Application configuration with Extended template configuration alignment.