When using only the new permissions on the Creator hub “Creator Roles” that allow administration of OpenCloud Keys, API Key scopes we tried to edit were declined…
Website shows “Network error has occured”, while the actual api response is 403.
When granted permissions using a classic role, issue is no longer present.
Expected behavior
If someone is assigned a creator role with OpenCloud permissions, they should be able to manage api keys and their scopes, not just view them.
Hey, sorry for the late reply on this, I also saw what you wrote in the private message which helped.
We were able to repro this and your bug report is correct, we require certain classic group permissions on API key creation/update for specific scopes/permissions such as the messaging service scope.
We looked into if we could bugfix this on a quick time frame, but unfortunately these classic permission checks are woven very deep into the code for API keys and scope registration. We plan to address it somewhere this year by moving this to use the new permissions instead, but just wanted to set the expectation that we likely can’t fix it very soon yet.