EAA Client supports these third-party identity providers (IdPs) in addition to the ​Akamai​ identity providers:

• Third-party SAML (like Shibboleth)
• Okta
• PingOne
• OneLogin

Below procedure shows how to configure Okta as an identity provider for EAA Client. Follow it's steps to enable the EAA Client to configure other IdPs (Shibboleth, PingOne, or OneLogin).

Add Okta as an identity provider for EAA Client

Configure Okta as an identity provider for EAA Client.

Prerequisite:
An Okta identity provider in EAA. See [Add Okta as an identity provider in EAA] (docs:integrate-okta)

1. Select Enable EAAClient to allow the Okta IdP to be used with the EAA Client.

2. If you have Enable Authorization selected, you can allow certain groups of users access the application. When selected, the directory has to be configured and assigned to the IdP.

3. If you have Enable Authorization deselected, all authenticated users from the third-party IdPs are allowed to access the applications associated with this identity provider.

4. Add a directory for the identity provider.

5. Assign identity providers to an application.