Identity Backend Template — Features (agents)

Agent intent

Know which optional stacks exist (OTel, Redis, HangFire, etc.) to match blueprint YAML.

Template role: User directory — accounts, roles, profiles. Pair with Authorization Server for OIDC issuance.

Canonical technical documentation

Full prose, diagrams, and edge cases live in ConnectSoft.Documentation:

➜ Features — public doc

Repository

• Repo: ConnectSoft.IdentityTemplate — README.md, AGENTS.md
• Installer (typical): ConnectSoft.IdentityTemplate.Installer
• Short name (typical): connectsoft-identity — confirm with dotnet new connectsoft-identity -h when applicable.

Agent checklist

• Prefer public doc for long explanations; keep Factory responses actionable and short.
• Do not embed secrets in generated appsettings; use env / KeyVault patterns per platform.

• Cross-link Template Architecture when touching DI or layering.

• See Template Architecture for DI layering.

Related (this repo)

• Overview
• Topic hub