mirror of
https://github.com/taigrr/nats.docs
synced 2025-01-18 04:03:23 -08:00
GitBook: [master] 211 pages modified
This commit is contained in:
parent
560e07b6a2
commit
f1382bc80f
@ -327,7 +327,7 @@ To obtain an Account JWT, the nats-server is configured with one of three [resol
|
|||||||
* Changes to the operator still require reloading \(only a few operations require that\).
|
* Changes to the operator still require reloading \(only a few operations require that\).
|
||||||
* Will download Accounts from a web server.
|
* Will download Accounts from a web server.
|
||||||
* Allows for easy publication of account JWTs programmatically generated using NKEYs and the JWT library.
|
* Allows for easy publication of account JWTs programmatically generated using NKEYs and the JWT library.
|
||||||
* The [`nats-account-server`](https://github.com/nats-io/nats.docs/tree/3fbe9e253a7b2fbf18766cd6f41fe0e866548868/developing-with-nats/nats-tools/nas/README.md) is such a webserver. When set up correctly, it will inform `nats-server` of Account JWT changes.
|
* The [`nats-account-server`](../../nats-tools/nas/) is such a webserver. When set up correctly, it will inform `nats-server` of Account JWT changes.
|
||||||
* Depending on configuration, requires read and/or write access to persistent storage.
|
* Depending on configuration, requires read and/or write access to persistent storage.
|
||||||
* `nats-resolver`: Same as `url-resolver`, just uses NATS instead of http
|
* `nats-resolver`: Same as `url-resolver`, just uses NATS instead of http
|
||||||
* No separate binary to run/config/monitor.
|
* No separate binary to run/config/monitor.
|
||||||
|
@ -41,7 +41,7 @@ The NATS based resolver embeds the functionality of the [account server](https:/
|
|||||||
|
|
||||||
### Full
|
### Full
|
||||||
|
|
||||||
The Full resolver stores all JWTs and exchanges them in an eventually consistent way with other resolvers of the same type. [`nsc`](../../../../nats-tools/nsc/) supports push/pull/purge with this resolver type. [JWTs](https://github.com/nats-io/nats.docs/tree/8c85d9c047d2203c7867b62a8415cdfa4d117f04/nats-server/configuration/nats-server/configuration/securing_nats/jwt/README.md), uploaded this way, are stored in a directory the server has exclusive access to.
|
The Full resolver stores all JWTs and exchanges them in an eventually consistent way with other resolvers of the same type. [`nsc`](../../../../nats-tools/nsc/) supports push/pull/purge with this resolver type. [JWTs](./), uploaded this way, are stored in a directory the server has exclusive access to.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
resolver: {
|
resolver: {
|
||||||
@ -85,7 +85,7 @@ resolver: {
|
|||||||
|
|
||||||
### NATS Based Resolver - Integration
|
### NATS Based Resolver - Integration
|
||||||
|
|
||||||
The NATS based resolver utilizes the system account for lookup and upload of account [JWTs](https://github.com/nats-io/nats.docs/tree/8c85d9c047d2203c7867b62a8415cdfa4d117f04/nats-server/configuration/nats-server/configuration/securing_nats/jwt/README.md) . If your application requires tighter integration you can make use of these subjects for tighter integration.
|
The NATS based resolver utilizes the system account for lookup and upload of account [JWTs](./) . If your application requires tighter integration you can make use of these subjects for tighter integration.
|
||||||
|
|
||||||
To upload or update any generated account JWT without [`nsc`](../../../../nats-tools/nsc/), send it as a request to `$SYS.REQ.CLAIMS.UPDATE`. Each participating `full` NATS based account resolver will respond with a message detailing success or failure.
|
To upload or update any generated account JWT without [`nsc`](../../../../nats-tools/nsc/), send it as a request to `$SYS.REQ.CLAIMS.UPDATE`. Each participating `full` NATS based account resolver will respond with a message detailing success or failure.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user