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
I'm not sure if this belongs here or in the main repo, but I see the issue in the console.
Expected Behavior
I should have access to update my own token.
Current Behavior
Access is denied when pressing update
Possible Solution
Give users permission to update their own access tokens
Steps to Reproduce (for bugs)
Create a user without admin:UpdateServiceAccount (I tested with the default readonly role)
Use that user to create an access token
Again use that user to try an update the token
Context
I am trying to update an access token without recreating it.
Regression
I don't think so.
Your Environment
MinIO version used (minio --version):
minio version RELEASE.2024-09-22T00-33-43Z (commit-id=03e996320ebb887112fb2a15c6f27936e5f124a0)
Runtime: go1.22.7 linux/amd64
License: GNU AGPLv3 - https://www.gnu.org/licenses/agpl-3.0.html
Copyright: 2015-2024 MinIO, Inc.
Server setup and configuration: Running in podman across 3 servers.
Operating System and version (uname -a): Linux minio 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered:
I'm not sure if this belongs here or in the main repo, but I see the issue in the console.
Expected Behavior
I should have access to update my own token.
Current Behavior
Access is denied when pressing update
Possible Solution
Give users permission to update their own access tokens
Steps to Reproduce (for bugs)
admin:UpdateServiceAccount
(I tested with the default readonly role)Context
I am trying to update an access token without recreating it.
Regression
I don't think so.
Your Environment
minio --version
):uname -a
):Linux minio 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: