GitBook: [master] 61 pages modified

nats-server/configuration/sys_accounts/README.md

@@ -1,6 +1,6 @@
-# System Events and Services
+# System Events
 
-NATS servers leverage [Accounts](../../configuration/securing_nats/accounts.md) support and generate events such as:
+NATS servers leverage [Accounts](../securing_nats/accounts.md) support and generate events such as:
 
 * account connect/disconnect
 * authentication errors
@@ -9,12 +9,12 @@ NATS servers leverage [Accounts](../../configuration/securing_nats/accounts.md)
 
 In addition the server supports a limited number of requests that can be used to query for account connections, server stat summaries, and pinging servers in the cluster.
 
-These events are enabled by configuring `system_account` and [subscribing/requesting](#Available-Events-and-Services) using a _system account_ user.
+These events are enabled by configuring `system_account` and [subscribing/requesting](./#Available-Events-and-Services) using a _system account_ user.
 
-[Accounts](../../configuration/securing_nats/accounts.md) are used so that subscriptions from your applications, say `>`, do not receive system events and vice versa.
-Using accounts requires either:
-* [Configuring authentication locally](#Local-Configuration) and listing one of the accounts in `system_account`
-* Or by using decentralized authentication and authorization via [jwt](../../configuration/securing_nats/jwt/README.md) as shown in this [Tutorial](sys_accounts.md). In this case `system_account` contains the account public key.
+[Accounts](../securing_nats/accounts.md) are used so that subscriptions from your applications, say `>`, do not receive system events and vice versa. Using accounts requires either:
+
+* [Configuring authentication locally](./#Local-Configuration) and listing one of the accounts in `system_account`
+* Or by using decentralized authentication and authorization via [jwt](../securing_nats/jwt/) as shown in this [Tutorial](https://github.com/nats-io/nats.docs/tree/aecb86faf9be946a413d1c6200fc0ff5d1b0baef/nats-server/configuration/sys_accounts/sys_accounts.md). In this case `system_account` contains the account public key.
 
 ## Available Events and Services
 
@@ -30,7 +30,7 @@ Server initiated events:
 * `$SYS.ACCOUNT.<id>.LEAFNODE.DISCONNECT` \(leaf node disconnects\)
 * `$SYS.SERVER.<id>.STATSZ` \(stats summary\)
 
-In addition other tools with system account privileges, can initiate requests (Examples can be found [here](sys_accounts.md#System-Services)):
+In addition other tools with system account privileges, can initiate requests \(Examples can be found [here](https://github.com/nats-io/nats.docs/tree/aecb86faf9be946a413d1c6200fc0ff5d1b0baef/nats-server/configuration/sys_accounts/sys_accounts.md#System-Services)\):
 
 * `$SYS.REQ.SERVER.<id>.STATSZ` \(request server stat summary\)
 * `$SYS.REQ.SERVER.PING` \(discover servers - will return multiple messages\)
@@ -66,7 +66,5 @@ accounts: {
 system_account: SYS
 ```
 
-Please note that applications now have to authenticate such that a connection can be associated with an account.
-In this example username and password were chosen for simplicity of the demonstration. 
-Subscribe to all system events like this `nats-sub -s nats://admin:changeit@localhost:4222 ">"` and observe what happens when you do something like `nats-pub -s "nats://a:a@localhost:4222" foo bar`. 
-Examples on how to use system services can be found [here](sys_accounts.md#System-Services).
+Please note that applications now have to authenticate such that a connection can be associated with an account. In this example username and password were chosen for simplicity of the demonstration. Subscribe to all system events like this `nats-sub -s nats://admin:changeit@localhost:4222 ">"` and observe what happens when you do something like `nats-pub -s "nats://a:a@localhost:4222" foo bar`. Examples on how to use system services can be found [here](sys_accounts.md#system-services).
+

nats-server/configuration/sys_accounts/sys_accounts.md

@@ -1,11 +1,13 @@
-# Enabling System Events with Decentralized Authentication/Authorization
+# System Events & Decentralized JWT Tutorial
+
+## Enabling System Events with Decentralized Authentication/Authorization
 
 To enable and access system events, you'll have to:
 
 * Create an Operator, Account and User
 * Run a NATS Account Server \(or Memory Resolver\)
 
-## Create an Operator, Account, User
+### Create an Operator, Account, User
 
 Let's create an operator, system account and system account user:
 
@@ -29,7 +31,7 @@ Success! - added user "SYSU" to "SYS"
 
 By default, the operator JWT can be found in `~/.nsc/nats/<operator_name>/<operator.name>.jwt`.
 
-## NATS-Account-Server
+### NATS-Account-Server
 
 To vend the credentials to the nats-server, we'll use a [nats-account-server](../../../nats-tools/nas/). Let's start a nats-account-server to serve the JWT credentials:
 
@@ -39,7 +41,7 @@ To vend the credentials to the nats-server, we'll use a [nats-account-server](..
 
 The server will by default vend JWT configurations on the an endpoint at: `http(s)://<server_url>/jwt/v1/accounts/`.
 
-## NATS Server Configuration
+### NATS Server Configuration
 
 The server configuration will need:
 
@@ -76,7 +78,7 @@ Let's start the nats-server:
 > nats-server -c server.conf
 ```
 
-# Inspecting Server Events
+## Inspecting Server Events
 
 Let's add a subscriber for all the events published by the system account:
 
@@ -136,9 +138,9 @@ The subscriber will print the connect and disconnect:
 }'
 ```
 
-# System Services
+## System Services
 
-## `$SYS.REQ.SERVER.PING` - Discovering Servers
+### `$SYS.REQ.SERVER.PING` - Discovering Servers
 
 To discover servers in the cluster, and get a small heath summary, publish a request to `$SYS.REQ.SERVER.PING`. Note that while the example below uses `nats-req`, only the first answer for the request will be printed. You can easily modify the example to wait until no additional responses are received for a specific amount of time, thus allowing for all responses to be collected.
 
@@ -175,7 +177,7 @@ Received  [_INBOX.G5mbsf0k7l7nb4eWHa7GTT.omklmvnm] : '{
 }'
 ```
 
-## `$SYS.SERVER.<id>.STATSZ` - Requesting Server Stats Summary
+### `$SYS.SERVER.<id>.STATSZ` - Requesting Server Stats Summary
 
 If you know the server id for a particular server \(such as from a response to `$SYS.REQ.SERVER.PING`\), you can query the specific server for its health information: