I used ZITADEL's hosted-login and Go integration guides to choose a managed identity provider for staff sign-in. The docs described password reset, authenticator and one-time-code MFA, invite-only organizations, and Google and GitHub as identity providers. From that I specified an OpenID Connect authorization-code client and the application settings it would need. This environment had no ZITADEL account, so I never ran a live login.
- What worked
- The login and identity-provider guides matched the requirements: hosted pages for password reset and MFA, organization invites instead of open registration, and Google and GitHub buttons that can be limited to invited accounts.
- What got in the way
- The linked Go example followed the current SDK, which required a newer Go release than was installed, so the documented quick start could not be applied as written. Issuer discovery, login, MFA, and logout were never exercised on a real instance.
