taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Update developing-with-nats/tutorials/jwt.md

Browse Source 
Co-authored-by: Colin Sullivan <colin@synadia.com>
This commit is contained in:
Matthias Hanel 2021-02-15 12:43:51 -05:00 committed by GitHub
parent 6ef72752f1
commit d9e0c373f7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
developing-with-nats/tutorials/jwt.md
View File

@ -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.