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.

1. Add Okta as an identity provider in EAA.

2. In addition to the above steps, configure the following ADVANCED SETTINGS:

   1. Select Enable EAA Client to allow the Okta identity provider to be used with the EAA Client.

   2. If you have Enable Authorization selected, it lets the EAA administrator allow certain groups of users access to the application. When selected, the directory has to be configured and assigned to the identity provider.
      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.

3. Add a directory for the identity provider.

4. Assign identity providers to an application.

5. Optionally, if you want to assign any additional attributes, see Assign the Okta identity provider to an application and map attributes.