No, MinIO does not depend on any third-party KMS provider. You have three options here:

- Run MinIO without a KMS. In this case all IAM data will be stored in plain-text.
- Run MinIO with a single secret key. MinIO supports a static cryptographic key
  that can act as minimal KMS. With this method all IAM data will be stored
  encrypted. The encryption key has to be passed as environment variable.

次のようなユーザーインターフェイスが表示されます：

<img src="/img/tutorial/security/image07.png">

前回と同じ方法でアプリケーションの認可を行います。

次の認証情報を使用します：

Username: `johndoe`
Password: `secret`

/// check | 確認

コードのどこにも平文のパスワード"`secret`"はなく、ハッシュ化されたものしかないことを確認してください。

///

<img src="/img/tutorial/security/image08.png">

エンドポイント`/users/me/`を呼び出すと、次のようなレスポンスが得られます：

```JSON
{

        when(response.getCommand()).thenReturn(command);
        response.setCommand(command);
        assertEquals(command, response.getCommand());

        // Test other setter methods
        doNothing().when(response).setUid(1000);
        response.setUid(1000);
        verify(response).setUid(1000);

        doNothing().when(response).setExtendedSecurity(true);

if [ $? -ne 0 ]; then
	echo "policy mapping missing, exiting.."
	exit_1
fi

# LDAP simple user
./mc admin user svcacct add minio2 dillon --access-key testsvc --secret-key testsvc123
if [ $? -ne 0 ]; then
	echo "adding svc account failed, exiting.."
	exit_1
fi

sleep 10

./mc idp ldap policy entities minio1
./mc idp ldap policy entities minio2

* Error while tearing down pod, "device or resource busy" on service account secret ([28750](https://github.com/kubernetes/kubernetes/issues/28750))



# v1.3.2

[Documentation](http://kubernetes.github.io) & [Examples](http://releases.k8s.io/release-1.3/examples)

## Downloads

        @Override
        public boolean isError() {
            return this.error;
        }

        @Override
        public void error() {
            this.error = true;
        }

        // Setter methods for testing
        public void setGrantedCredits(int grantedCredits) {
            this.grantedCredits = grantedCredits;
        }

        public void setErrorCode(int errorCode) {

        SmbComNegotiateResponse smb1 = new SmbComNegotiateResponse(ctx);
        setField(transport, "negotiated", smb1);
        assertFalse(transport.isSMB2());
    }

    @Test
    @DisplayName("Digest setter/getter roundtrip")
    void digestRoundtrip() {
        SMBSigningDigest dg = mock(SMBSigningDigest.class);
        transport.setDigest(dg);
        assertSame(dg, transport.getDigest());
    }

    @Test

            this.rawPayload = payload;
        }

        public byte[] getRawPayload() {
            return rawPayload;
        }

        // Helper method to set credit since parent's setter is final
        public void setCreditForTest(int credit) {
            setCredit(credit);
        }

        @Override
        public Smb2SigningDigest getDigest() {
            return digest;
        }

### Configure Keycloak Realm

- Go to Clients
  - Click on account
    - Settings
    - Change `Access Type` to `confidential`.
    - Save
  - Click on credentials tab
    - Copy the `Secret` to clipboard.
    - This value is needed for `MINIO_IDENTITY_OPENID_CLIENT_SECRET` for MinIO.

- Go to Users
  - Click on the user

     */
    public String getKey() {
        return key;
    }

    /**
     * Sets the key.
     *
     * @param key
     *            the key
     */
    public void setKey(final String key) {
        this.key = key;
    }

    /**
     * Returns the charset name.
     *
     * @return the charset name
     */
    public String getCharsetName() {