We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocking
Confirmed in 2023.2 (Build 2719-hotfix.3744)
I could reproduce the problem in the latest build
Users are unable to generate or view the "My API Keys" page without ConfigureServer permissions
Ensure a user has no "System Permissions"
While logged in as the user, attempt to navigate to the "My API Keys" page for the user
You should see the following error
Add the ConfigureServer permission to the user
You should see the page as normal
No response
Unfortunately, the only workaround is to temporarily grant the user ConfigureServer permissions.
The text was updated successfully, but these errors were encountered:
Release Note: Rolled back extra permission requirements when viewing API keys
Sorry, something went wrong.
🎉 The fix for this issue has been released in:
tothegills
No branches or pull requests
Severity
Blocking
Version
Confirmed in 2023.2 (Build 2719-hotfix.3744)
Latest Version
I could reproduce the problem in the latest build
What happened?
Users are unable to generate or view the "My API Keys" page without ConfigureServer permissions
Reproduction
Ensure a user has no "System Permissions"
While logged in as the user, attempt to navigate to the "My API Keys" page for the user
You should see the following error
Add the ConfigureServer permission to the user
While logged in as the user, attempt to navigate to the "My API Keys" page for the user
You should see the page as normal
Error and Stacktrace
No response
More Information
No response
Workaround
Unfortunately, the only workaround is to temporarily grant the user ConfigureServer permissions.
The text was updated successfully, but these errors were encountered: