### Cache the OpenAPI schema { #cache-the-openapi-schema }

You can use the property `.openapi_schema` as a "cache", to store your generated schema.

That way, your application won't have to generate the schema every time a user opens your API docs.

It will be generated only once, and then the same cached schema will be used for the next requests.

{* ../../docs_src/extending_openapi/tutorial001_py39.py hl[13:14,25:26] *}

        CANONICAL_PROTOCOLS.put("vfsfile", "file"); // Proprietary protocol used by JBossAS5 for file system
    }

    /**
     * Opens a URL and returns an {@link InputStream}.
     *
     * @param url
     *            The URL. Must not be {@literal null}.
     * @return An {@link InputStream} to read the resource represented by the URL.
     */

          // https://security.stackexchange.com/questions/35639/decrypting-tls-in-wireshark-when-using-dhe-rsa-ciphersuites
          // https://stackoverflow.com/questions/36240279/how-do-i-extract-the-pre-master-secret-using-an-openssl-based-client

          // TLSv1.2 Events
          // Produced ClientHello handshake message
          // Consuming ServerHello handshake message
          // Consuming server Certificate handshake message

        final FileEntry[] results = this.response.getResults();
        if (results == null) {
            return new FileEntry[0];
        }
        return results;
    }

    /**
     * Opens a directory for enumeration
     *
     * @return the opened directory file entry
     * @throws CIFSException if an error occurs opening the directory
     */
    @SuppressWarnings("resource")
    @Override

 *
 * <p>
 * There are three Win32 function calls provided by the Windows SDK
 * that are important in the context of using jCIFS. They are:
 *
 * <ul>
 * <li><code>CallNamedPipe</code> A message-type pipe call that opens,
 * writes to, reads from, and closes the pipe in a single operation.
 * <li><code>TransactNamedPipe</code> A message-type pipe call that
 * writes to and reads from an existing pipe descriptor in one operation.

Um einen sicheren zufälligen geheimen Schlüssel zu generieren, verwenden Sie den folgenden Befehl:

<div class="termy">

```console
$ openssl rand -hex 32

09d25e094faa6ca2556c818166b7a9563b93f7099f6f0f4caa6cf63b88e8d3e7
```

</div>

Und kopieren Sie die Ausgabe in die Variable `SECRET_KEY` (verwenden Sie nicht die im Beispiel).

Importa los módulos instalados.

Crea una clave secreta aleatoria que se usará para firmar los tokens JWT.

Para generar una clave secreta segura al azar usa el comando:

<div class="termy">

```console
$ openssl rand -hex 32

09d25e094faa6ca2556c818166b7a9563b93f7099f6f0f4caa6cf63b88e8d3e7
```

</div>

Y copia el resultado a la variable `SECRET_KEY` (no uses la del ejemplo).

                doClose();
                return null;
            }
            this.ridx = 0;
            return advance(true);
        }
        return null;
    }

    /**
     * Opens the enumeration and returns the first entry.
     *
     * @return the first file entry, or null if empty
     * @throws CIFSException if an error occurs during opening
     */

        // Act + Assert (no exception expected)
        assertDoesNotThrow(() -> SmbCopyUtil.copyFile(src, dest, buffers, 1, new WriterThread(), sh, dh));

        // Verify that server-side path engaged at least the initial opens
        verify(src, times(1)).openUnshared(anyInt(), anyInt(), anyInt(), anyInt(), anyInt());
        verify(dest, times(1)).openUnshared(anyInt(), anyInt(), anyInt(), anyInt(), anyInt());
    }

Создайте случайный секретный ключ, который будет использоваться для подписи JWT-токенов.

Для генерации безопасного случайного секретного ключа используйте команду:

<div class="termy">

```console
$ openssl rand -hex 32

09d25e094faa6ca2556c818166b7a9563b93f7099f6f0f4caa6cf63b88e8d3e7
```

</div>

И скопируйте полученный результат в переменную `SECRET_KEY` (не используйте тот, что в примере).