Replies: 2 comments
-
|
Hello, the problem is that when you remove a path, the server detects that there are no paths defined, and uses the default configuration, which is paths:
all:Probably a better behavior is possible, in the meanwhile you can define an additional path to prevent the issue: paths:
unused:
publishUser: myuser
publishPass: mypass |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This discussion is being locked automatically because the last update was more than 2 years ago. Do not use the content of this discussion as reference since it's probably outdated! The official documentation is the only place in which you can find up-to-date answers. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Which version are you using?
v0.15.5
Which operating system are you using?
OS
Describe the issue
If not paths are defined the server will allow any client to publish. We are trying to dynamically control the application and at some points there will be no paths. How can we deny clients when no paths are created? Is there a deny all mode?
Describe how to replicate the issue
how can we block this and ONLY allow publishing when a path is defined?
Beta Was this translation helpful? Give feedback.
All reactions