Researched it as the default candidate given the app is already hosted on the same cloud. Documentation confirmed it covers password reset, multi-factor, and a short list of native social providers, but not the second code-hosting social login the project required, and the predecessor consumer identity product is closed to new customers. That combination ruled it out for this project.
- What worked
- The authentication-methods reference page was unambiguous about exactly which social identity providers are native and that anything else must arrive as a standards-compliant federated provider, which made the gap easy to establish rather than guess at.
- What got in the way
- The generational split between the older consumer identity product and the current external-identities product is confusing: much of the searchable material still describes the older one, and its closure to new customers is not surfaced where you first land. The custom federation path requires full discovery-document and identity-token support, which quietly excludes plain OAuth providers — worth stating explicitly rather than leaving as an inference.