mirror of
https://github.com/gogrlx/nats-server.git
synced 2026-04-16 11:04:42 -07:00
01057467cf
Similar as with clients, this makes it possible to
use the subject from a TLS certificate to validate
the permissions from a cluster member.
Currently only a single configured user is supported:
```
cluster {
tls {
cert_file = "./configs/certs/tlsauth/server.pem"
key_file = "./configs/certs/tlsauth/server-key.pem"
ca_file = "./configs/certs/tlsauth/ca.pem"
verify_and_map = true
timeout = 2
}
permissions {
publish {
allow = ["public.>"]
}
subscribe {
allow = ["public.>"]
}
}
authorization {
user = "CN=localhost,OU=NATS.io Operators"
}
}
```
Signed-off-by: Waldemar Quevedo <wally@synadia.com>
24 lines
404 B
Plaintext
24 lines
404 B
Plaintext
|
|
cluster {
|
|
tls {
|
|
cert_file = "./configs/certs/tlsauth/server.pem"
|
|
key_file = "./configs/certs/tlsauth/server-key.pem"
|
|
ca_file = "./configs/certs/tlsauth/ca.pem"
|
|
verify_and_map = true
|
|
timeout = 2
|
|
}
|
|
|
|
permissions {
|
|
publish {
|
|
allow = ["public.>"]
|
|
}
|
|
subscribe {
|
|
allow = ["public.>"]
|
|
}
|
|
}
|
|
|
|
authorization {
|
|
user = "CN=localhost,OU=NATS.io Operators"
|
|
}
|
|
}
|