You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The customer has a requirement to delete shared scopes from the shared scopes list in the API publisher. However, the delete button is disabled, indicating a number of usages for the scope, but the usage list appears empty when clicked.
Steps to Reproduce:
Start an APIM 4.1.0 pack and log in to the publisher (tested with admin user).
Create multiple shared scopes (e.g., team:create, team:update) and assign the role of admin.
Deploy the Pizza Shack API and assign scopes to deploy the revision.
Remove the scopes and deploy a new revision.
Go to the resources, remove the scopes, and deploy it again.
Go to the shared scope tab and observe the issue mentioned.
Conclusion:
This issue appears to be related to revisions. When a new revision is deployed without scopes, references to the scopes remain in previous revisions.
If this is the expected behavior, the system should at least show the APIs and revisions using the scopes.
From local testing, we observed that even after deleting the scopes from previous revisions, it still shows one usage left on the shared scopes page.
Thank you.
Best regards
Solution
Update to the UI that displays which revision the scope is linked to, making it easier to remove.
Affected Component
APIM
Version
4.1.0.133
Implementation
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Problem
Hello team,
The customer has a requirement to delete shared scopes from the shared scopes list in the API publisher. However, the delete button is disabled, indicating a number of usages for the scope, but the usage list appears empty when clicked.
team:create
,team:update
) and assign the role of admin.This issue appears to be related to revisions. When a new revision is deployed without scopes, references to the scopes remain in previous revisions.
If this is the expected behavior, the system should at least show the APIs and revisions using the scopes.
From local testing, we observed that even after deleting the scopes from previous revisions, it still shows one usage left on the shared scopes page.
Thank you.
Best regards
Solution
Update to the UI that displays which revision the scope is linked to, making it easier to remove.
Affected Component
APIM
Version
4.1.0.133
Implementation
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: