From 6723e87802da01f30d4e0941bbcd6cb8bf51003b Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Mon, 30 Mar 2020 14:30:31 -0400 Subject: [PATCH] Fix links Signed-off-by: Matthias Hanel --- nats-server/configuration/securing_nats/jwt/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nats-server/configuration/securing_nats/jwt/README.md b/nats-server/configuration/securing_nats/jwt/README.md index c07ebbb..da620db 100644 --- a/nats-server/configuration/securing_nats/jwt/README.md +++ b/nats-server/configuration/securing_nats/jwt/README.md @@ -17,12 +17,12 @@ Claims are a fancy way of asserting information on a _subject_. In this context, 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](auth_intro/nkey_auth.md). +* NATS adopts the convention that all _Issuer_ and _Subject_ fields in a JWT claim must be a public [NKEY](../auth_intro/nkey_auth.md). * _Issuer_ and _Subject_ must match specific roles depending on the claim [NKeys](https://github.com/nats-io/nkeys). ### NKey Roles -[NKeys](auth_intro/nkey_auth.md) Roles are: +[NKeys](../auth_intro/nkey_auth.md) Roles are: * Operators * Accounts