Jean-Gabriel Gill-Couture
75aac243c7
All checks were successful
Run Check Script / check (pull_request) Successful in 2m18s
Step-by-step for wiring the operator dashboard's browser SSO: the Zitadel app settings the code requires (Web app, PKCE/no-secret, redirect + post-logout URIs), each config value mapped to its source (ZitadelAuthConfig + cookie key), how to provide them (staging via FleetDeployConfig/Secrets with hosts derived from base_domain; local via HARMONY_CONFIG_* env), the derived endpoints, and the common-failure gotchas (iss/aud/redirect mismatch, no client secret, localhost dev mode, ≥64-byte cookie key). Grounded in harmony_zitadel_auth's login/jwks code. Registered in SUMMARY and cross-linked from web-auth-security.
2.6 KiB
2.6 KiB
Summary
Use Cases
Component Catalogs
Developer Guides
- Developer Guide
- Writing a Score
- Writing a Topology
- Adding Capabilities
- Web Authentication and CSRF Security
- Operator Dashboard SSO (Zitadel) — setup
Configuration
Architecture Decision Records
- ADR Overview
- 000 · ADR Template
- 001 · Why Rust
- 002 · Hexagonal Architecture
- 003 · Infrastructure Abstractions
- 004 · iPXE
- 005 · Interactive Project
- 006 · Secret Management
- 007 · Default Runtime
- 008 · Score Display Formatting
- 009 · Helm and Kustomize Handling
- 010 · Monitoring and Alerting
- 011 · Multi-Tenant Cluster
- 012 · Project Delivery Automation
- 013 · Monitoring Notifications
- 015 · Higher Order Topologies
- 016 · Harmony Agent and Global Mesh
- 017-1 · NATS Clusters Interconnection
- 018 · Template Hydration for Workload Deployment
- 019 · Network Bond Setup
- 020 · Interactive Configuration Crate
- 020-1 · Zitadel + OpenBao Secure Config Store