We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Resgate should be able to connect to NATS server using NATS user credential files.
The scope only covers user credential files, and will not include TLS certificates.
Other methods, such as token and username/password authentication, are already supported as the url can contain username/password semantics. Eg.:
resgate --nats nats://user:[email protected]:4222
A command-line option should be added:
--creds
An option should be added to the configuration file:
natsCreds (string) NATS User Credentials file. Example: "~/ngs.creds"
"~/ngs.creds"
The text was updated successfully, but these errors were encountered:
Support for user credential files was initially added in #63
Sorry, something went wrong.
GH-108: Fixed command flag naming.
d27470d
Merge pull request #109 from resgateio/feature/gh-108-support-nats-us…
73f1a35
…er-credentials Feature/gh 108 support nats user credentials
Resolved in #109
jirenius
No branches or pull requests
Issue
Resgate should be able to connect to NATS server using NATS user credential files.
Note
The scope only covers user credential files, and will not include TLS certificates.
Other methods, such as token and username/password authentication, are already supported as the url can contain username/password semantics. Eg.:
Implementation
A command-line option should be added:
--creds
- NATS User Credentials file.An option should be added to the configuration file:
natsCreds (string)
NATS User Credentials file.
Example:
"~/ngs.creds"
The text was updated successfully, but these errors were encountered: