Syntax Example The following command retrieves the JSON-formatted anonymous policy for the mydata bucket on the myaistor MinIO AIStor deployment: mc anonymous get-json myaistor/mydata Syntax The command has the following syntax:

The mc anonymous set command sets anonymous (that is, unauthenticated or public) access policies for a bucket. Buckets with anonymous policies allow clients to access the bucket contents and perform actions consistent with the specified policy without authentication. To set anonymous bucket policies using an IAM JSON policy, use the mc anonymous set-json command. Syntax Example The following command sets the anonymous access policy for the mydata bucket on the myaistor MinIO AIStor deployment:

The mc alias set command sets or updates an alias in the AIStor Client configuration. Syntax Example The following command sets an alias named myaistor:

The mc admin user disable command disables an MinIO AIStor user on the target MinIO AIStor deployment. Clients cannot use the user credentials to authenticate to the MinIO AIStor deployment. Disabling a user does not remove that user from the deployment. Use mc admin user enable to enable a disabled user on an MinIO AIStor deployment. To manage external Identity Provider users, see OIDC or AD/LDAP.

mc idp ldap accesskey edit modifies the specified access key on the local server. Syntax Example The following example modifies the secret for the access key mykey on the myaistor deployment:

The mc alias list command lists all configured aliases in the AIStor Client configuration. Syntax Example The following command lists all aliases:

The mc idp ldap accesskey ls displays a list of LDAP access key pairs. mc idp ldap accesskey ls is also known as mc idp ldap accesskey list. This command works against access keys created by an AD/LDAP user after authenticating to MinIO AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the MinIO AIStor Console. MinIO AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

The mc idp ldap commands allow you to manage configurations to 3rd party Active Directory or LDAP Identity and Access Management (IAM) integrations. MinIO AIStor supports multiple named LDAP configurations, allowing you to integrate with different directory services or organizational units within your environment. Multiple LDAP Configurations Support for multiple LDAP configurations requires AIStor Server version RELEASE.2025-12-20T04-58-37Z or later and AIStor Client (mc) version RELEASE.2025-12-19T20-11-44Z or later. The mc idp ldap commands are an alternative to using environment variables when setting up an AD/LDAP connection. They are only supported for MinIO AIStor clusters. See Active Directory / LDAP Access Management for a tutorial on using these commands.

The mc idp ldap rm command removes an AD/LDAP IDP server configuration from an MinIO AIStor deployment. Syntax Example The following example removes the default AD/LDAP configuration for the myaistor deployment.

The mc idp openid disable command stops your MinIO AIStor deployment from using an existing OIDC configuration. Example and syntax Example The following example disables the server configurations defined as test_config on the myaistor deployment.