build-logic/kotlin-dsl-shared-runtime/                      @gradle/bt-tide
platforms/core-configuration/kotlin-dsl/                    @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-integ-tests/        @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-plugins/            @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-provider-plugins/   @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-tooling-builders/   @gradle/bt-tide

## FAQ

> Why is this change needed?

Before, there were two separate mechanisms - S3 objects got encrypted using a KMS,
if present, and the IAM / configuration data got encrypted with the root credentials.
Now, MinIO encrypts IAM / configuration and S3 objects with a KMS, if present. This

    "crossVersionTests": false
  },
  {
    "name": "configuration-cache",
    "path": "platforms/core-configuration/configuration-cache",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "configuration-cache-base",
    "path": "platforms/core-configuration/configuration-cache-base",
    "unitTests": false,
    "functionalTests": false,

            <option value="$PROJECT_DIR$/platforms/core-configuration/configuration-cache-base" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/configuration-problems-base" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/core-flow-services-api" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/core-kotlin-extensions" />

    - Save

- Go to Users
  - Edit the user
    - Add your MinIO policy (ex: `readwrite`) in `Tag`
    - Save

- Open your favorite browser and visit: **http://`CASDOOR_ENDPOINT`/.well-known/openid-configuration**, you will see the OIDC configure of Casdoor.

### Configure MinIO

```
export MINIO_ROOT_USER=minio
export MINIO_ROOT_PASSWORD=minio123
minio server /mnt/export
```

package cmd

import (
	"os"
	"path/filepath"

	homedir "github.com/mitchellh/go-homedir"
)

const (
	// Default minio configuration directory where below configuration files/directories are stored.
	defaultMinioConfigDir = ".minio"

	// Directory contains below files/directories for HTTPS configuration.
	certsDir = "certs"

	// Directory contains all CA certificates other than system defaults for HTTPS.
	certsCADir = "CAs"

The MinIO-KES configuration is always the same - regardless of the underlying KMS implementation. Checkout the MinIO-KES [configuration example](https://github.com/minio/kes/wiki/MinIO-Object-Storage).

### Further references

- [Run MinIO with TLS / HTTPS](https://docs.min.io/community/minio-object-store/operations/network-encryption.html)
- [Tweak the KES server configuration](https://github.com/minio/kes/wiki/Configuration)

	"github.com/minio/minio/internal/logger"
	"github.com/minio/mux"
	"github.com/minio/pkg/v3/policy"
)

const (
	// Bucket Encryption configuration file name.
	bucketSSEConfig = "bucket-encryption.xml"
)

// PutBucketEncryptionHandler - Stores given bucket encryption configuration
// https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketEncryption.html

	"github.com/minio/minio/internal/logger"
	"github.com/minio/mux"
	"github.com/minio/pkg/v3/policy"
)

const (
	// Lifecycle configuration file.
	bucketLifecycleConfig = "lifecycle.xml"
)

// PutBucketLifecycleHandler - This HTTP handler stores given bucket lifecycle configuration as per
// https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html

      {{- end }}
      volumes:
        - name: etc-path
          emptyDir: {}
        - name: tmp
          emptyDir: {}
        - name: minio-configuration
          projected:
            sources:
              - configMap:
                  name: {{ template "minio.fullname" . }}
              - secret:
                  name: {{ template "minio.secretName" . }}