Access applications from EAA Login Portal

Users access applications from the Enterprise Application Access (EAA) Login Portal. You can also access applications from the EAA Login Portal to see changes after you deploy the applications.

  1. Open a browser window on any device that has Internet connectivity and is not connected to your internal network. This saves some aggravation if there are additional configuration steps required in your network to reach outside applications (for example, Firewall or Secure Web Gateway configurations).

  2. Enter the external URL of the application you created. For example, https://eaa-acme-app.go.akamai-access.com.

  3. Log in with the username and password assigned to the directory.
    In the case of Active Directory/LDAP, use your AD credentials to login.

Use EAA application portal with third party IdP and allow users to access applications

Allow Enterprise Application Access (EAA) application portal as the portal for the third party IdPs which do not have a user portal. When you use a third party IdP like Shibboleth or AD FS which do not have a user portal, you can use the EAA application portal and organize your applications. The applications are displayed in a table and you can filter them by the category they belong to or by any other information type from the column headers.
When the users authenticate with a third party IdP, they are directed to the EAA application page, or redirected to another URL. You can also enable authorization in the third party IdP to allow Enterprise Application Access to enforce authorization policy based on user groups to an application. This allows Enterprise Application Access to get the user from the SAML assertion, which is the NameID attribute in the SAML attributes sent by the third party IdP and allows mapping to the AD in the ‚ÄčAkamai‚Äč database. This functionality enables Enterprise Application Access to do the user authorization on behalf of the third party IdP, without set access control rules (ACLs) for applications like Azure or AD FS.

  1. Log in to EAA Management Portal.

  2. In the EAA Management Portal navigation menu, select Identity > Identity providers.

  3. On the third party identity provider card, click Configure Identity Provider.

  4. In GENERAL > Authentication configuration > URL.
    When it is blank, the EAA application portal is used. You can enter a different URL to redirect the application portal URL.

  5. In Settings > Advanced select Enable Authorization, to allow Enterprise Application Access to do the user authentication.

  6. In DIRECTORIES click Assign directory.
    The list of configured directories opens.

  7. Select the directory to assign it to the IdP.

  8. In ADVANCED SETTINGS > Advanced, select Enable Authorization, to allow Enterprise Application Access to do the user authentication.

  9. Click Save and go to Deployment.

  10. Deploy the IdP.

When the user logs in to the third party IdP, after authentication, they are redirected to the ‚ÄčAkamai‚Äč application portal. Based on their particular group access permissions, the respective application cards are displayed.


Did this page help you?