6cd6d7cc79
CRITICAL FIX: Ensures all three flow blueprints are deployed during initial setup The issue was that only custom-flows.yaml was being deployed, but enrollment-flow.yaml and recovery-flow.yaml were created separately and manually deployed later. This caused problems when servers were rebuilt - the enrollment and recovery flows would disappear. Changes: - Updated flows.yml to deploy all three blueprints in a loop - enrollment-flow.yaml: Invitation-only user registration - recovery-flow.yaml: Password reset via email - custom-flows.yaml: 2FA enforcement and brand settings Now all flows will be available immediately after deployment: ✓ https://auth.dev.vrije.cloud/if/flow/default-enrollment-flow/ ✓ https://auth.dev.vrije.cloud/if/flow/default-recovery-flow/ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bootstrap.yml | ||
| docker.yml | ||
| email.yml | ||
| flows.yml | ||
| invitation.yml | ||
| main.yml | ||
| mfa.yml | ||
| providers.yml | ||