taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

syntax & grammar review

Browse Source
This commit is contained in:
Ginger Collison 2021-06-16 16:31:17 -05:00 committed by GitHub
parent 8a9f7247d4
commit 9cd2de8795
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
nats-server/configuration/ocsp.md
View File

@ -16,7 +16,7 @@ tlsfeature = status_request
...
```
The NATS server will make a request to the OCSP responder to fetch a new staple which will be then presented to
The NATS server will make a request to the OCSP responder to fetch a new staple which will then be presented to
any TLS connection that is accepted by the server during the TLS handshake.
OCSP Stapling can be explicitly enabled or disabled in the NATS Server by setting the following flag in the NATS configuration file:
@ -28,24 +28,24 @@ ocsp: false
**Note**: When OCSP Stapling is disabled, the NATS Server will not request staples even if the certificate has
the Must-Staple flag.
## Advanced configuration
## Advanced Configuration
By default, the NATS Server will be running in OCSP `auto` mode. In this mode the server will only fetch
staples when the Must-Staple flag is configured in the certificate.
There are a other different OCSP modes that control the behavior on whether OCSP should be enforced and server
should shutdown if the cert runs with a revoked staple:
There are other OCSP modes that control the behavior as to whether OCSP should be enforced and the server
should shutdown if the certificate runs with a revoked staple:
| Mode | Description | Server shutdowns when revoked |
| --------- | ---- | ----- |
| auto | Enables OCSP Stapling when it has the must staple/status_request flag | No |
| must | Enables OCSP Staping when it has the must staple/status_request flag | Yes |
| auto | Enables OCSP Stapling when the certificate has the must staple/status_request flag | No |
| must | Enables OCSP Staping when the certificate has the must staple/status_request flag | Yes |
| always | Enables OCSP Stapling for all certificates | Yes |
| never | Disables OCSP Stapling even if must staple flag is present (same as `ocsp: false` | No |
| never | Disables OCSP Stapling even if must staple flag is present (same as `ocsp: false`) | No |
For example, in the following configuration OCSP, the mode is set to `must`. This means that staples will be fetched only for certificates
that have the Must-Staple flag enabled as well, but in case of revokation the server will shutdown rather than run with a revoked staple.
In this configuration, the `url` will also override OCSP responder URL that may have been configured in
For example, in the following OCSP configuration, the mode is set to `must`. This means that staples will be fetched only for certificates
that have the Must-Staple flag enabled as well, but in case of revocation the server will shutdown rather than run with a revoked staple.
In this configuration, the `url` will also override the OCSP responder URL that may have been configured in
the certificate.
```hcl
@ -55,7 +55,7 @@ ocsp {
}
```
In case staples are always required regardless of the configuration of the certificate, then this can be enforced as follows:
If staples are always required, regardless of the configuration of the certificate, you can enforce the behavior as follows:
```hcl
ocsp {
@ -64,11 +64,11 @@ ocsp {
}
```
## Caching of staples
## Caching of Staples
When a `store_dir` is configured in the NATS Server, the directory will be used to cache staples on disk
to allow the server to resume in case of restarts without having to make another request to the OCSP responder
in case the staple is still valid.
if the staple is still valid.
```hcl
store_dir: "/path/to/store/dir"