From d9e0c373f7bfdbd4183411f85cc9cfd9a88c05c4 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Mon, 15 Feb 2021 12:43:51 -0500 Subject: [PATCH] Update developing-with-nats/tutorials/jwt.md Co-authored-by: Colin Sullivan --- developing-with-nats/tutorials/jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/tutorials/jwt.md b/developing-with-nats/tutorials/jwt.md index 27e25f5..c102b1e 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -280,7 +280,7 @@ Connection closed by foreign host. In a large organization the centralized config approach can lead to less flexibility/resistance to change when controlled by one entity. Alternatively, instead of operating one infrastructure, it can be deployed more often (say per team) thus making import/export relationships harder as they have to bridge separate systems. -In order to make accounts truly powerful, they should ideally be configured separately from the infrastructure, only constraint by limits. +In order to make accounts truly powerful, they should ideally be configured separately from the infrastructure, only constrained by limits. Similar for user. An account contains user but this relationship could be a reference as well, such that alterations to user do not alter the account. User of the same account should be able to connect from anywhere in the same infrastructure and be able to exchange messages as long as they are in the same authentication domain.