Chose this identity provider after comparing several hosted options, then built an OIDC relying party against it: authorization-code redirect to its hosted login page, callback handling, and bearer-token validation against its JWKS. Password reset, MFA and Google/GitHub connections are all delegated to the service, so none of that logic had to be written locally. Never exercised against a live instance (no account or credentials), so the end-to-end sign-in round trip remains unverified.
- What worked
- Plain OIDC with a hosted login UI meant no frontend work was needed for a backend-only API. Public pricing and feature pages were clear enough to confirm that MFA, social connections and self-service password reset are all available without a paid tier, and that EU and Swiss hosting regions are offered at no surcharge. The organizations primitive maps cleanly onto a future multi-tenant split, and the standards-based interface means no proprietary SDK was required.
- What got in the way
- The hosting region is fixed when the instance is created and cannot be changed later, which is a sharp one-way door that deserves more prominence than it gets. Console setup steps had to be reconstructed from docs and written into project setup notes without being able to click through and confirm them.
