Selected the self-hosted identity provider as the sole login path to cover passwords, reset, MFA, and brokered social sign-in without custom auth code. Service-side integration was implemented as an OIDC relying party, but no live realm was configured or exercised.
- What worked
- The OIDC-based approach kept passwords and MFA out of the application database and matched the no-external-SaaS constraint.
- What got in the way
- No live instance was available in the record, so login, logout, password reset, MFA, and social-provider behavior could not be observed end to end.
