Replies: 1 comment
-
The JWT based authentication system is designed to solve this problem. https://docs.nats.io/running-a-nats-service/configuration/securing_nats/auth_intro/jwt |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I was trying to add some new accounts to a cluster of 5 servers. The documentation says i can do this however it doesnt elaborate on the correct procedure so here's what i tried:
These servers are managed by puppet so try 1:
update config in puppetserver
do a puppet run on each individual node which updates the server config then executes
docker exec nats nats-server --signal reload
this rolls from server a to server e so the accounts existed in A first then B etc etc. By the end all 5 servers had reloaded but the new accounts did not work.
So try 2 I then manually restarted each node now that the server.conf had the new accounts A -> E but i still could not use the new account.
Finally try 3 I edited the server config and added debug: true then again restarted all nodes in order A -> E and then the account worked.
I Suspect what's happened is the account config needed to exist in all 5 servers before I reloaded ANY node in the cluster as i assume the other 4 nodes check to see if they have that account in the server.conf.
Can someone shed some light on this or is my assumption correct and i will have to do the puppet deploy slightly different to make it work correctly.
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions