Selected ZITADEL as the staff identity provider and shaped the service as an OpenID Connect relying party so password reset, MFA, and Google and GitHub login would stay in that product. The material consulted was the Go SDK reference, which showed a current release that needs a newer Go than this module, so the client was written against generic OpenID Connect libraries. No ZITADEL instance was installed or signed into; tests used a fake issuer, and live login was left for a later tenant setup.
- What worked
- The product's described scope (hosted login, email password reset, TOTP and passkeys, and external identity providers) matched the staff requirements and kept those flows out of the service. Issuer, client credentials, redirect URL, and a session key were enough to define the relying-party configuration.
- What got in the way
- Setup never reached a running instance, so password reset, MFA enforcement, and social sign-in were not observed. The official Go client path was unusable on the module's Go version.
