Federated or third-party authorization server support with OAuth 2.0 server
Federated or third-party authorization server support with OAuth 2.0 server
You can implement OAuth 2.0 authentication using federated or third-party providers such as, Okta and Azure AD, to secure your APIs effectively. This configuration enhances API security by leveraging external OAuth identity providers. You can streamline the authentication process, making it easier for developers to integrate secure access controls.
You can enable your API consumers to access protected resources using tokens generated from their preferred OAuth provider without pre-provisioning all API consumers through the IDMC identity provider.
You can fetch JWT access tokens from the identity provider and include the tokens in login requests. Before you use JWT access tokens, complete the following tasks:
In IDMC, configure the organization to use SAML and set up users as SAML users.
Set up an OAuth identity provider. You can use identity providers such as Azure Active Directory and Okta.
In
API Center
, register the authorization server of the third-party identity service for authentication. For more information. see
Register an authorization server.
In
API Center
, assign the third-party users to specific APIs for authorization.
To log in, you need to obtain a JWT access token from the identity provider and include the token in a loginOAuth POST request. The token can be used for one REST API session. If the login request is successful, the response includes a session ID to use in subsequent API calls.
For information about OAuth setup using Azure Active Directory, see the following article:
Set up OAuth with Azure AD
For information about OAuth setup using Okta, see the following article:
Set up OAuth with Okta
For more information about identity provider configuration, see the identity provider's documentation.
For more information about registering identity providers and logging in using JWT access tokens, see
REST API Reference.
ASK INFAPreview
