This article discusses some of the problems you might encounter when working with custom providers. More importantly, it also explains what you need to do to fix those problems.
In this section of the documentation
- The button for my custom provider appears on the Hosted Login sign-in screen, but nothing happens when I click that button.
- I added my custom provider to the authentication.providers.custom setting, but the button for that provider doesn’t appear in the Hosted Login sign-in screen.
- The button for my custom provider appears in the Hosted Login sign-in screen, but that button has a name that looks like this: 3cc14467-fd4f-437d-a0c0-0b3888dd2ee4.d284e861-d7f9-426e-93b0-56e01cf6d0ea.
- I’m able to log on to my social login identity provider, but that doesn’t log me on to Hosted Login.
- When users employ my custom provider to create a new account, they’re able to authenticate with the social login provider and are redirected back to Hosted Login. However, none of the information on the Complete Your Registration screen is filled in for them. In my custom provider, I’ve requested the email and the address scopes, but none of that information is being returned.
- In my custom provider, I’ve requested the email and the address scopes, but none of this information is being returned.
- I’m trying to create an OpenID Connect custom provider for a social login identity provider. However, I can’t find that provider’s token endpoint or their userinfo endpoint anywhere in their documentation.