Melden Sie sich bei der Anwendung auf die gleiche Weise wie zuvor an.

Verwenden Sie die Anmeldeinformationen:

Benutzername: `johndoe`
Passwort: `secret`.

/// check

Beachten Sie, dass im Code nirgendwo das Klartext-Passwort "`secret`" steht, wir haben nur die gehashte Version.

///

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

    <glob pattern="*.setpay"/>
  </mime-type>
  <mime-type type="application/set-registration"/>
  <mime-type type="application/set-registration-initiation">
    <glob pattern="*.setreg"/>
  </mime-type>
  <mime-type type="application/sgml"/>
  <mime-type type="application/sgml-open-catalog"/>
  <mime-type type="application/shf+xml">
    <glob pattern="*.shf"/>
  </mime-type>

        /**
         * @return String
         */
        public String getEee() {
            return null;
        }

        /**
         * @param eee
         */
        public void setEee(final String eee) {
        }

        /**
         * @return int
         */
        public int getFff() {
            return fff_;
        }

        /**
         * @param fff

            referralData.setKey("test-key");
            referralData.replaceCache();
            assertEquals(referralData, cacheMap.get("test-key"));
        }

        @Test
        @DisplayName("Should replace cache entry with key")
        void testReplaceCache() {
            String key = "cache-key";
            referralData.setKey(key);
            referralData.setCacheMap(cacheMap);

## 2. Create Kubernetes secret

[Kubernetes secrets](https://kubernetes.io/docs/concepts/configuration/secret) are intended to hold sensitive information.
We'll use secrets to hold the TLS certificate and key. To create a secret, update the paths to `private.key` and `public.crt`
below.

Then type

```sh

        final PathMapping pathMapping1 = new PathMapping();
        pathMapping1.setRegex("file:///home/");
        pathMapping1.setReplacement("http://localhost/");
        pathMappingList.add(pathMapping1);

        final PathMapping pathMapping2 = new PathMapping();
        pathMapping2.setRegex("http://localhost/");
        pathMapping2.setReplacement("https://server/");

```

### MinIO Custom Access and Secret Keys using Docker secrets

To override MinIO's auto-generated keys, you may pass secret and access keys explicitly by creating access and secret keys as [Docker secrets](https://docs.docker.com/engine/swarm/secrets/). MinIO server also allows regular strings as access and secret keys.

```
echo "AKIAIOSFODNN7EXAMPLE" | docker secret create access_key -

displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...

#### Cryptographic Primitives

displayed in the output of a successful install. Existing secret ---------- Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret...