You're viewing Apigee Edge documentation.
View Apigee X documentation.
On Monday, August 21, 2017, we began releasing a new cloud version of Developer Services Portal.
The following bug is fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
|DEVSOL-2625||Monetization roles getting dropped after switching company
If you have monetization enabled, if you assign a role to a user and they switch from one company context to another, the role is no longer removed from the user.
Drupal modules updates
The following Drupal modules were updated to the release indicated:
"Website encountered an error" message displayed while enabling
This error is no longer logged.
|DEVSOL-2609||Drupal status page does not show proper Edge connection status for SAML
Drupal Status page now shows proper Edge connection status for SAML (OAuth). Previously, the Reports > Status reports page would show the connection was not working even if you had SAML properly configured.
|DEVSOL-2608||SAML/OAuth: Log prints Bearer token cache miss with every call
Fixed issue with Bearer token cache logic that was causing system to get a new token each time it called Edge.
|DEVSOL-2599||Multiple issues with devconnect_user_developer_is_active()
Fixed issue where the wrong developer's status was checked to decide if the user is active or not. If a developer account is disabled in the Edge UI causing the app keys to stop working, the system will now display a message to inform the developer. Also added performance improvements to this functionality.
SAML configuration enhancements and updates
The following enhancements and updates have been made to the SAML configuration:
|DEVSOL-2569||App Analytics: Endpoint Response Time is no longer working, changed to Total
Endpoint Response Time analytics graph has been removed from the Analytics tab on the Developer apps page since it did not reflect total response time and was causing confusion. The metric was reflecting only the time it took for the endpoint to respond, but not the time it took the API proxy to respond. The Throughput graph displays the total response time for end developers.