Then if you run into any issues with the third-party provider, you just "disable" the integration and do a normal email-based password reset flow.
Then if you run into any issues with the third-party provider, you just "disable" the integration and do a normal email-based password reset flow.
You could have the user register by providing an email and clicking a verification link, and then optionally allow em to link third-party services. Regular account access is allowed after authenticating through any available method, but administrative actions require going through the email flow. That way you reduce the risk from a compromised or malicious third-party. Of course, this would assume that email is a good identification authority, which isn't always the case.
You don't need that complex workflow; most third-party authentication services allow you to also request the user's email address during the initial process.
I don't think some of these alleged identity providers should have as much power and trust as they have.