21.01.07 - Apigee Edge integrated portal release notes

Unable to link to API category from navigation menu

You can now link to an API category from a navigation menu using its full or relative URL.

API requests slow to respond, sometimes return 502

An issue has been fixed that was causing API requests to be slow to respond.

Improve security of JSESSIONID cookie

The JSESSIONID cookie, which identifies the browser session to the server, now has the flags HttpOnly and Secure set to true. This increases the portal's security against malicious users.

Update configuration to use HttpOnly and Secure flags on cookies

The HttpOnly and Secureflags are set to true for the portalRefresh and portalSession cookies. In addition, the Secure flag is set to true for the X-Apigee-CSRF flag. (To ensure proper function, the HttpOnly flag is set to false, in this case.)

API details page: Audience display issues

Minor formatting improvements have been implemented in the Audience section on the API details page. Specifically:

• Anonymous users (anyone can view) is selected by default when adding an API
• Options are listed as a single column of radio buttons

Developer emails should not be case-sensitive for members of developer teams

Developer emails are no longer case-sensitive for members of developer teams.

Organization administrator not able to view developer account information with error "Visibility of PII is restricted by role"

An issue has been fixed that was preventing organization administrators from viewing developer account information.

Nested menu item with no parent breaks portal

Previously, you could publish a header or footer menu that contained a nested item without a parent, but it would prevent the portal from rendering. Now an error is thrown if you attempt to publish a menu with a nested item that does not have a parent.

Changing a portal page URL breaks any assigned audience permissions

Previously, if a page path was modified, then all its associated permissions were lost and the page was invisible to everyone. Now when a page path is modified the associated permissions are maintained.