MinIO

Tested Versions#

• Authelia
  • v4.39.1
• MinIO
  • 2025-03-12T18-04-18Z

Before You Begin#

Common Notes#

1. The OpenID Connect 1.0 client_id parameter:
   1. This must be a unique value for every client.
   2. The value used in this guide is merely for readability and demonstration purposes and you should not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
   3. This must only contain RFC3986 Unreserved Characters.
   4. This must be no more than 100 characters in length.
2. The OpenID Connect 1.0 client_secret parameter:
   1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ.
   2. This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
   3. When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of hashing can, if too great, cause timeouts for clients. See the Tuning the work factors guide for more information.
3. The configuration example for Authelia:
   1. Only contains an example configuration for the client registration and you MUST also configure the required elements from the OpenID Connect 1.0 Provider Configuration guide.
   2. Only contains a small portion of all of the available options for a registered client and users may wish to configure portions that are not part of this guide or configure them differently, as such it’s important to both familiarize yourself with the other options available and the effect of each of the options configured in this section by looking at the OpenID Connect 1.0 Clients Configuration guide.

Assumptions#

This example makes the following assumptions:

• Application Root URL: https://minio.example.com/
• Authelia Root URL: https://auth.example.com/
• Client ID: minio
• Client Secret: insecure_secret

Some of the values presented in this guide can automatically be replaced with documentation variables.

Set Documentation Variables

Configuration#

Authelia#

The following YAML configuration is an example Authelia client configuration for use with MinIO which will operate with the application example:

identity_providers:
  oidc:
    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    clients:
      - client_id: 'minio'
        client_name: 'MinIO'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        redirect_uris:
          - 'https://minio.example.com/oauth_callback'
        scopes:
          - 'openid'
          - 'profile'
          - 'email'
          - 'groups'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'

Application#

To configure MinIO there are two methods, using Environment Variables, or using the Web GUI.

Environment Variables#

To configure MinIO to utilize Authelia as an OpenID Connect 1.0 Provider, use the following environment variables:

Standard#

MINIO_IDENTITY_OPENID_CONFIG_URL=https://auth.example.com/.well-known/openid-configuration
MINIO_IDENTITY_OPENID_CLIENT_ID=minio
MINIO_IDENTITY_OPENID_CLIENT_SECRET=insecure_secret
MINIO_IDENTITY_OPENID_SCOPES=openid,profile,email,groups
MINIO_IDENTITY_OPENID_REDIRECT_URI=https://minio.auth.example.com/oauth_callback
MINIO_IDENTITY_OPENID_REDIRECT_URI_DYNAMIC=off
MINIO_IDENTITY_OPENID_DISPLAY_NAME=Authelia
MINIO_IDENTITY_OPENID_CLAIM_NAME=groups
MINIO_IDENTITY_OPENID_CLAIM_USERINFO=on

Docker Compose#

services:
  minio:
    environment:
      MINIO_IDENTITY_OPENID_CONFIG_URL: 'https://auth.example.com/.well-known/openid-configuration'
      MINIO_IDENTITY_OPENID_CLIENT_ID: 'minio'
      MINIO_IDENTITY_OPENID_CLIENT_SECRET: 'insecure_secret'
      MINIO_IDENTITY_OPENID_SCOPES: 'openid,profile,email,groups'
      MINIO_IDENTITY_OPENID_REDIRECT_URI: 'https://minio.auth.example.com/oauth_callback'
      MINIO_IDENTITY_OPENID_REDIRECT_URI_DYNAMIC: 'off'
      MINIO_IDENTITY_OPENID_DISPLAY_NAME: 'Authelia'
      MINIO_IDENTITY_OPENID_CLAIM_NAME: 'groups'
      MINIO_IDENTITY_OPENID_CLAIM_USERINFO: 'on'

Web GUI#

To configure MinIO to utilize Authelia as an OpenID Connect 1.0 Provider, use the following instructions:

1. Login to MinIO
2. On the left hand menu, go to Identity, then OpenID
3. On the top right, click Create Configuration
4. Configure the following options:
   • Name: authelia
   • Config URL: https://auth.example.com/.well-known/openid-configuration
   • Client ID: minio
   • Client Secret: insecure_secret
   • Claim Name: groups
   • Display Name: Authelia
   • Claim Prefix: Leave Empty
   • Scopes: openid,profile,email,groups
   • Redirect URI: https://minio.example.com/oauth_callback
   • Role Policy: Leave Empty
   • Claim User Info: Enabled
   • Redirect URI Dynamic: Disabled
5. Press Save at the bottom
6. Accept the offer of a server restart at the top
   • Refresh the page and sign out if not done so automatically
7. Add your user to an authelia group that matches the policy name in MinIO. There are select default policies that can be used. (The group name and policy name must match.)
8. When the login screen appears again, click the Other Authentication Methods open, then select Authelia from the list.
9. Login

Additional Steps#

You may also want to consider adding a default policy to your user groups in Authelia.

See Also#

• MinIO OpenID Identity Management