I added my custom provider to the authentication.providers.custom setting. So why doesn't the button for that provider appear on the Hosted Login sign-in screen?
We’re assuming that you’re seeing something similar to this, where you have two standard providers (Facebook and Google) that display in the sign-in screen, and a custom provider that doesn't display in the sign-in screen:
This is typically the result of forgetting to add your custom provider to the authentication.providers setting:
As you no doubt guessed, the way to fix this problem is to, well, add your custom provider to the authentication.providers setting:
And yes, that does look a little weird, But that's because you can't specify a custom provider by using a name like Okta. Instead, you have to use a special identifier (like 3cc14467-fd4f-437d-a0c0-0b3888dd2ee4.d284e861-d7f9-426e-93b0-56e01cf6d0ea) pieced together from the following items:
Your Akamai customer ID (3cc14467-fd4f-437d-a0c0-0b3888dd2ee4).
A period (.).
The custom provider’s id (d284e861-d7f9-426e-93b0-56e01cf6d0ea). This is the ID assigned to the provider when it was created.
That should solve the problem:
Updated over 1 year ago