Identity Backend Template — Configuration (agents)

Agent intent

appsettings / env naming must follow extended template alignment across Acceptance vs Application.

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:

➜ Configuration — 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.

• HangFire / SQL catalog naming is a common drift hotspot (Authorization Server).

Related (this repo)

• Overview
• Topic hub