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
Note: This is occurring within the official Docker image. I have not tested it with directly running minio outside of Docker.
When logging into the MinIO console as the root user, the user should have all privileges.
Current Behavior
On RELEASE.2022-07-29T19-40-48Z, when the root user logs in the user has no privileges - cannot create buckets, see settings, access any objects, etc. The list of buckets can be obtained, and pseudo-directories can be viewed within buckets, but no actual objects can be viewed.
This was tested on a fresh new instance of MinIO, as described below.
Login to the MinIO console using the root user account. (I've deliberately used insecure credentials here, but it's reproducible with any credentials.)
Try to create a bucket and note that the Create Bucket option is disabled. Also note that most options in the left sidebar do not exist. The root account appears to have no privileges and is being treated like an anonymous user.
The mc admin trace command outputs the following when the user logs in:
This does not appear to impact access to the S3 backend itself. In testing so far it only appears to affect the MinIO integrated console.
Regression
This appears to be a regression. Downgrading to RELEASE.2022-07-24T17-09-31Z resolves the issue and the console can again be accessed using the root account.
Your Environment
Version used (minio --version): RELEASE.2022-07-24T17-09-31Z
Server setup and configuration:
Docker version 20.10.16, build aa7e414fdcb23a66e8fabbef0a560ef1769eace5
Docker Compose version v2.6.0
ZFS filesystem for storage
x86_64 architecture
Operating System and version (uname -a): Alpine Linux as bare-metal OS on primary test system. Reproduced on Ubuntu 22.04 as well.
The text was updated successfully, but these errors were encountered:
Expected Behavior
Note: This is occurring within the official Docker image. I have not tested it with directly running minio outside of Docker.
When logging into the MinIO console as the root user, the user should have all privileges.
Current Behavior
On RELEASE.2022-07-29T19-40-48Z, when the root user logs in the user has no privileges - cannot create buckets, see settings, access any objects, etc. The list of buckets can be obtained, and pseudo-directories can be viewed within buckets, but no actual objects can be viewed.
This was tested on a fresh new instance of MinIO, as described below.
Possible Solution
For now, downgrading to RELEASE.2022-07-24T17-09-31Z has temporarily fixed the issue.
Steps to Reproduce (for bugs)
docker-compose.yml
file to start up a simple MinIO instance:Login to the MinIO console using the root user account. (I've deliberately used insecure credentials here, but it's reproducible with any credentials.)
Try to create a bucket and note that the Create Bucket option is disabled. Also note that most options in the left sidebar do not exist. The root account appears to have no privileges and is being treated like an anonymous user.
The
mc admin trace
command outputs the following when the user logs in:Context
This does not appear to impact access to the S3 backend itself. In testing so far it only appears to affect the MinIO integrated console.
Regression
This appears to be a regression. Downgrading to
RELEASE.2022-07-24T17-09-31Z
resolves the issue and the console can again be accessed using the root account.Your Environment
minio --version
):RELEASE.2022-07-24T17-09-31Z
Docker version 20.10.16, build aa7e414fdcb23a66e8fabbef0a560ef1769eace5
Docker Compose version v2.6.0
x86_64
architectureuname -a
): Alpine Linux as bare-metal OS on primary test system. Reproduced on Ubuntu 22.04 as well.The text was updated successfully, but these errors were encountered: