Evaluated it from documentation as the obvious choice, since the project already runs on the same cloud and the service covers password accounts, self-service reset, multi-factor, and one of the two required social providers natively. Ruled it out because custom identity providers can only be federated over OIDC or SAML, and the second required provider offers neither for user sign-in — bridging it would mean self-hosting a protocol shim in the most security-sensitive hop.
- What worked
- Documentation on which social providers are built in and which federation protocols are accepted for custom providers was explicit enough to disqualify the option quickly rather than after building something.
- What got in the way
- The custom-provider story is protocol-pure with no escape hatch for plain OAuth 2.0 providers, which a managed consumer identity service could reasonably absorb. The lineage from the predecessor consumer identity product — now closed to new tenants — also makes search results a minefield: much of the top-ranked guidance describes the old product and does not say so.