From 0e257e096fd4ebd96e3ef6f01d2dc17a765cec74 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jaime=20Pi=C3=B1a?= Date: Sat, 5 Sep 2020 20:42:48 -0700 Subject: [PATCH] Fix typo --- nats-server/configuration/securing_nats/jwt/jwt_nkey_auth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/securing_nats/jwt/jwt_nkey_auth.md b/nats-server/configuration/securing_nats/jwt/jwt_nkey_auth.md index 1f634b8..795000d 100644 --- a/nats-server/configuration/securing_nats/jwt/jwt_nkey_auth.md +++ b/nats-server/configuration/securing_nats/jwt/jwt_nkey_auth.md @@ -1,6 +1,6 @@ # Mixed Authentication/Authorization Setup -Mixing both [nkeys](../auth_intro/nkey_auth.md) static config and [decentralized JWT Authenticatin/Authorization](./) is possible but needs some preparation in order to be able to do it. +Mixing both [nkeys](../auth_intro/nkey_auth.md) static config and [decentralized JWT Authentication/Authorization](./) is possible but needs some preparation in order to be able to do it. The way this can be done is by **first** preparing a basic trusted operator setup that could be used in the future, and then base from that configuration to create the NKEYS static config using the same shared public nkeys for the accounts and then use clustering routes to bridge the two different auth setups during the transition.