20.08.05 - Apigee Edge integrated portal release notes

Error when activating/deactivating developer account

An issue has been fixed in the UI that was causing an error similar to the following (which could be ignored) when activating/deactivating a developer account:
Unable to update user status

External spec URLs do not support redirects

When importing an OpenAPI Specification using a URL redirects will not be followed.

Duplicate developer programs created and unable to delete

Developer programs that are not in use by an integrated portal will no longer be displayed.

Portals with audience management (beta) enabled display empty page for restricted pages

Improved experience for non-signed in users for portals enrolled in audiences management.

Delete all artifacts when deleting a developer program

When deleting a developer program, all artifacts that associated with the developer program, including developer teams or audiences, are also deleted.

APIs page style changes

The following changes have been implemented on the APIs page:

• The Filter by title and description field now appears above API cards and spans the top of the page allowing for better visibility of API cards on small screens and 4 API cards to fit per row on a fully expanded browser window
• API cards on the APIs page have been made more responsive using CSS Grid Layout

Miscellaneous security fixes

Recaptcha error for v1 integrated portals when clicking sign up via login page

An issue has been fixed that was causing a recaptcha validation error when attempting to create an account in a v1 integrated portal.

Request header Content-type: application/json is getting added to GET request

An issue has been fixed that was causing the Content-type: application/json to be added to GET requests.

Read access to developer account information should not be available to all users

Read access to developer account information is now controlled by role, and redacted for users that do not have organization adminstrator or portaladmin roles.

OpenAPI Spec with media type of application/json-patch+json does not render in SmartDocs and
SmartDocs does not support formData parameters

The APIs Explorer widget now allows for text input for more request body MIME types, including JSON mime types ending with "+json", "application/xml", "application/x-www-form-urlencoded". The full list of mime types that support text input can be found here: https://github.com/codemirror/CodeMirror/blob/master/mode/meta.js#L15-L172