A MinIO user consists of a unique access key (username) and corresponding secret key (password). Clients must authenticate their identity by specifying both a valid access key (username) and the corresponding secret key (password) of an existing MinIO user.
Each user can have one or more assigned policies that explicitly list the actions and resources to which that user has access. Users can also inherit policies from the groups in which they have membership.
MinIO by default denies access to all actions or resources not explicitly allowed by a user’s assigned or inherited policies . You must either explicitly assign a policy describing the user’s authorized actions and resources or assign the user to groups which have associated policies. See Access Management for more information.
This page documents user management for the MinIO internal IDentity Provider (IDP). MinIO also external management of identities using either an OpenID Connect (OIDC) or Active Directory/LDAP IDentity Provider (IDP). For more information, see:
Enabling external identity management disables the MinIO internal IDP, with the exception of creating access keys .
MinIO Access Keys (formerly “Service Accounts”) are child identities of an authenticated MinIO user, including externally managed identities . Each access key inherits its privileges based on the policies attached to it’s parent user or those groups in which the parent user has membership. Access keys also support an optional inline policy which further restricts access to a subset of actions and resources available to the parent user.
A MinIO user can generate any number of access keys. This allows application owners to generate arbitrary access keys for their applications without requiring action from the MinIO administrators. Since the generated access keys have the same or fewer permissions as the parents, administrators can focus on managing the top-level parent users without micro-managing generated access keys.
Access Keys are for Programmatic Access
Access Keys support programmatic access by applications. You cannot use an access key to log into the MinIO Console.
MinIO deployments have a
user with access to all actions and resources
on the deployment, regardless of the configured
. When a
starts, it sets the
user credentials by checking the value of the
following environment variables:
Rotating the root user credentials requires updating either or both variables
for all MinIO servers in the deployment. Specify
long, unique, and random
strings for root credentials. Exercise all possible precautions in storing the
access key and secret key, such that only known and trusted individuals who
superuser access to the deployment can retrieve the
MinIO strongly discourages using the
rootuser for regular client access regardless of the environment (development, staging, or production).
MinIO strongly recommends creating users such that each client has access to the minimal set of actions and resources required to perform their assigned workloads.
If these variables are unset,
as the access key and secret key respectively. MinIO
use of the default credentials regardless of deployment
Deprecation of Legacy Root User Environment Variables
MinIO RELEASE.2021-04-22T15-44-28Z and later deprecates the following variables used for setting or updating root user credentials:
command to create a new user on the
mc admin user add ALIAS ACCESSKEY SECRETKEY
SECRETKEYwith the secret key for the user. MinIO does not provide any method for retrieving the secret key once set.
Specify a unique, random, and long string for both the
. Your organization may have specific internal or regulatory
requirements around generating values for use with access or secret keys.
mc admin policy set ALIAS readwrite user=USERNAME
created in the previous step.
command to remove a user on a
mc admin user remove ALIAS USERNAME