Evaluated first as the platform-native option since the project already runs on the same cloud. Its documentation lists a fixed set of supported external identity providers that does not include one of the two required social logins, and the generic federation escape hatch requires full discovery-based identity tokens that the required provider does not issue, so it could not meet the requirements.
- What worked
- The authentication-methods and identity-provider documentation enumerates supported providers explicitly, so ruling it out took one page rather than a trial tenant. Pricing and free-tier details were also documented clearly.
- What got in the way
- The supported-provider list is a hard boundary with no first-class bridge for a widely used provider that speaks only plain OAuth. The predecessor product that could handle this through custom policies is closed to new tenants, and the docs do not clearly flag that this migration removes that capability for new customers — which is exactly the thing a reader evaluating it needs to know up front.