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

dead links

Browse Source
This commit is contained in:
Alberto Ricart
2019-05-20 16:33:52 -05:00
parent c1f113449a
commit 2268002f81
124 changed files with 135 additions and 135 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
nats_server/jwt_auth.md
View File

@@ -27,7 +27,7 @@ NATS further restricts JWTs by requiring that JWTs be:
- Digitally signed _always_ and only using [Ed25519](https://ed25519.cr.yp.to/).
- NATS adopts the convention that all _Issuer_ and _Subject_ fields in a JWT claim must be a public [NKEY](nkey_auth.md).
- It also introduces type requirements into claims, enabling the pairing of specific roles matching those supported by [NKeys](https://github.com/nats-io/nkey).
- It also introduces type requirements into claims, enabling the pairing of specific roles matching those supported by [NKeys](https://github.com/nats-io/nkeys).
#### NKey Roles

2
nats_server/monitoring.md
View File

@@ -6,7 +6,7 @@ The NATS monitoring endpoints support JSONP and CORS, making it easy to create s
## Enabling monitoring
To enable the monitoring server, start the NATS server with the monitoring flag `-m` and the monitoring port, or turn it on in the [configuration file](/documentation/managing_the_server/configuration).
To enable the monitoring server, start the NATS server with the monitoring flag `-m` and the monitoring port, or turn it on in the [configuration file](configuration.md#configuration-properties).
-m, --http_port PORT HTTP PORT for monitoring
-ms,--https_port PORT Use HTTPS PORT for monitoring