Closed arunz6161 closed 3 years ago
This is kinda related to #115.
"Forbidden" at the beginning of the log message was a clear indication of the issue.
I agree that "Cannot reach management server" as an error message could be misleading because this error message indicates that the server could have been reached (connected error) but it could be reached and it returned an HTTP 403.
I think we should rather display different error messages on this error page for
We should never expose the raw HTTP responses (status codes, etc) or error messages from API response payloads (like "Developer with testelek@example.com email address not found." in #115) to simple authenticated users because these could potentially expose too many details that simple users should not know.
We could consider exposing more information in place to admins besides asking them to "check the configuration of this site" but we should define who we call as "an admin" in this sense:
admin/config/people/accounts
) - that user has access to everything in Drupal so it makes sense to chose this definition.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe. Noticed an issue when upon clicking on "Apps" as an external developer, error Cannot reach management server. An administrator should check the configuration of this site. was thrown. This was not helpful as the connection test on "Apigee edge general settings" page was returning successful test results. It was only when debug was enabled, the error indicated a possible issue with permissions:
Describe the solution you'd like The generic error Cannot reach management server seems to indicate a possible connectivity issue between portal and edge API which was not the case here. Better error translation is needed to quickly diagnose such issues.
Describe alternatives you've considered Enabling apigee debug module and then cross checking "devadmin" user permissions on edge helped narrow down the issue.
Additional context None.