Manage custom providers
Create and manage custom social login providers. Custom providers enable you to use almost any identity provider (IdP) for social logins and registrations as long as that IdP supports one of the following protocols:
- OAuth 2.0
- OpenID Connect
- SAML 2
Manage custom providers
-
Create a social login provider
Before you can create a custom provider you need to create an authentication app with the social login provider. For example if you want to use Slack as a social login provider then you need to go to the Slack developer site and create an app that allows users to log in to a site by using their Slack credentials. -
Select a social login application
Picking the social login application where the new custom provider will be created. -
Create a custom provider
Everything you need to know in order to create a custom provider. -
Map custom provider attributes
Map the fields returned from a custom provider (e.g., userFirstName) to their corresponding Identity Cloud user profile attributes (e.g., givenName). -
Enable a custom provider
Adding your new provider to Hosted Login. -
Modify the authn_context property
You might have to do this if your SAML2 provider respects the RequestedAuthnContext element. (most don't, but ....) -
List custom providers
Return a list of all your custom providers. -
View a custom provider
View detailed information for a custom provider. -
Modify a custom provider
There are two different ways (JSON merge patch and JSON patch) to modify a provider. Here's how both of those approaches work. -
Delete a custom provider
Quick answer: you can’t delete a custom provider. -
Use Etags to check for custom provider updates
Verify that you have the latest version of a custom provider. -
Create a SAML authentication application
A step-by-step guide to creating a SAML2 custom provider for Okta.
Updated about 2 years ago