Evaluated it first because the project is already hosted entirely on this vendor's cloud. Read the authentication-methods documentation and confirmed it covers email and password with self-service reset plus MFA, but its built-in social providers do not include the second one this project required, and the generic federation escape hatch could not cover that provider either. Ruled out on capability.
- What worked
- The supported-authentication-methods page is unambiguous and lists the built-in social providers explicitly, so the disqualifying fact took one page to establish rather than a trial integration. Documentation on the predecessor product's closure to new tenants was also easy to find.
- What got in the way
- The built-in social provider list is short, and the documented custom federation path assumes a fully compliant discovery document, which the provider we needed does not publish. The docs do not say that plainly, so it takes outside knowledge to realize the escape hatch is not an escape hatch. Overlapping generations of this vendor's customer identity products also make it harder than it should be to tell which one a new project is supposed to adopt.