AIStor requires authentication and authorization for every operation on the object store. Human users and client applications must authenticate, and can perform only operations on resources explicitly allowed by the access policies assigned to them. Authentication verifies the identity of a user or client application. User credentials take the form of a username and password. Application credentials can take the form of an access key and secret key, or an application can call the appropriate STS endpoint. Which endpoint depends on your identity provider.

The mc idp openid commands allow you to manage configurations for third-party OpenID Connect Identity and Access Management (OIDC IAM) integrations. You can create as many OIDC configurations as your environment requires. Define configuration settings as an alternative to using environment variables when setting up an OIDC connection. The mc idp openid commands are only supported against AIStor deployments. AIStor OIDC environment variables override their corresponding configuration settings as modified or set by this command.

The mc inventory list command lists all inventory configurations for a specified bucket. The command displays the inventory configurations in a table format showing the bucket name, configuration ID, and owner. You can optionally output the full YAML definitions for each configuration. This command has an alias: mc inventory ls. Syntax Example The following command lists all inventory configurations for bucket mybucket:

mc idp openid accesskey disable disables the specified access key on the AIStor deployment. Example and syntax Example The following example disables the access key mykey on the myaistor deployment:

The mc license info command displays information about the AIStor deployment’s license status. The command shows: Organization name License plan and trial status Organization-level storage capacity limit License issue and expiration dates License ID (if available) API key (if available) When a license is expired, the expiry date displays in red to highlight the issue. For complete information about license management and renewal procedures, see Licenses. Syntax Example mc license info myaistor The command displays the license status and expiration information.

The mc ilm rule command and its subcommands configure the rules used to transition objects between storage tiers in AIStor’s Lifecycle Management. Before creating rules with this command, use mc ilm tier and its subcommands to create the tier or tiers of other object storage locations where objects move. For more information, see the overview of lifecycle management. Subcommands mc ilm rule includes the following subcommands:

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

The mc idp ldap update command modifies an existing set of configurations for an AD/LDAP provider. Syntax Example The following example changes two of the default AD/LDAP configuration settings for the myaistor deployment.

The mc ilm rule add command adds an object lifecycle management rule to a bucket. Syntax The command supports adding both Transition (Tiering) and Expiration lifecycle management rules. Example The following command adds new lifecycle management rules to the mydata bucket on the myaistor deployment:

This page explains how to deploy AIStor with KES for Server Side Encryption. For instructions on running KES, see the KES docs. Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key.