-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add support for nats-account-server #234
Comments
This would be great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NATS provides NSC and JWT authentication [1]. I tried to setup
nats-account-server
[2] and unable to load its configuration regardless how I configure it, e.g. I tried URL and MEM resolvers (within a cluster and on dedicated node). With availablenats-account-server
I'm getting the following error innats-cluster
logs:It would be nice if you'll complement this request with appropriate documentation.
For completeness here is description of all my attempts.
I figure it out that
nats-cluster
secret containsnats.conf
which I can modify with my custom settings and re-create this secret. Once newnats.conf
is supplied andnats-cluster
secret is re-created then the server reloads its configuration according to newnats.conf
file.I tried these settings in
nats.conf
:nats-clients-tls
secret with my server certificates andTest.jwt
Test.jwt
was added to/etc/nats-server-tls-certs
nats.conf
to use these settings (I changed URL accordingly to my host):or
I also tried to deploy
nats-account-server
to my cluster and create Service for it, but I was not able to access it since I think nats-operator does not allow this and additional changes should be made to see k8s svc:port. Then I deployednats-account-server
on dedicated host and it still does not work for nats-cluster and produces the aforementioned issue.Thanks,
Valentin.
[1] https://docs.nats.io/nats-tools/nsc/nsc
[2] https://github.com/nats-io/nats-account-server
The text was updated successfully, but these errors were encountered: