Closed mxr576 closed 1 year ago
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.
Addressed as a part of #809
@giteshk Are you sure it was address? In #809 I only see modifications related to #766, but not for this one. I believe to fix this, the quoted code in the description needed to be changed.
@phdhiren to validate.
Description
We are investigating an issue with a customer that I haven't seen before in my long journey with Apigee. It looks like having
PUT
permission to the/developers
endpoint is not enough for the devportal to create developers on Apigee. (Permissions configured accordingly to this matrix: https://github.com/apigee/apigee-edge-drupal/blob/5857361da977b94d6fccc46f473f3f1958f3ab61/src/Command/Util/ApigeeEdgeManagementCliService.php#L140-L161)I have only spotted one "special" feature flag on the related Apigee org's configuration. Could it happen that the
features.keymanagement.disable.unbounded.permissions
feature flag has this additional side effect?According to the related changelog/documentation it should not be, but I have no other idea: https://docs.apigee.com/release/notes/180202-apigee-edge-public-cloud-release-notes
Or what other feature flag can cause this? Maybe the default permission matrix needs an audit in this module?
Apigee Info
Apigee Edge