configuration

name

configuration

description

caddy-security Caddyfile configuration generation for the security app and authenticate or authorize HTTP directives. Use when creating, reviewing, or modifying Caddyfile configs for authentication portals, authorization policies, identity stores, OAuth or SAML identity providers, SSO app providers, users, registration flows, messaging, credentials, secrets, or runtime replacement in this repository.

Configuration

Purpose

Use this skill as the entry point for generating caddy-security Caddyfile configuration. Keep the parent skill as a router: load only the domain skills needed for the requested configuration.

The authoritative parser entry point is caddyfile.go. The global block is security { ... }; route-level HTTP integrations reference configured objects with authenticate with <portal> and authorize with <policy>.

Do not generate global Caddy directive-order overrides for caddy-security by default. authenticate and authorize register their own order in plugin_authn.go and plugin_authz.go. Only add global order directives when debugging a proven directive-order conflict with another third-party plugin, and explain why.

Workflow

1. Identify the requested auth flow: local login, LDAP, OAuth/OIDC, SAML, API keys, basic auth, registration, SSO app, or policy-only authorization.
2. Load only the relevant configuration-* domain skills from the Domain Map before drafting the Caddyfile. Load configuration-http-integrations whenever adding route-level authenticate or authorize handlers. Load configuration-saml-providers for saml identity provider <name> blocks; do not substitute the SSO app skill. Load when the request involves Portal API, JSON login, , , or admin/server API endpoints.