Enterprise Application Access (EAA) updates.

​Akamai​ EAA new features

Duplicate Origin detection for Tunnel Applications. When you create a new client-access tunnel application with a Destination that already exists in another tunnel application associated with the same identity provider, a generic error message was shown, “The internal host has not been specified or internal hostname, port range and protocol combination is duplicate across the idp.” The fixed message provides more details of which application the duplication exists. When you hover over the error message details you can see the duplicate applications:

Fixed customer bugs

• The Enable session stickiness option under URL Path based policy was getting unchecked after making any additional configuration changes in Application’s Advanced Settings and deploying the application. This issue has been fixed.
• When creating a new url path-based policy the Internal Host header is not replicated to url policy even though "Use internal hostname" is checked. However, if you change Internal Host in main settings page, then the internal host value is replicated/pushed to all existing Url Path-based policies who have checked "use internal hostname".
• If you enable users from Disabled Users report, the message indicates the user is enabled back, but the user does not exist in the directory.
• Users that are disabled and deleted from the IdP/directory are still shown in the disabled report. This issue is fixed.