Skip to content
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

Able to deregister node via UI with acl_default_policy = deny on Consul 0.6.3 #1708

Closed
ashald opened this issue Feb 10, 2016 · 2 comments
Closed

Comments

@ashald
Copy link
Contributor

ashald commented Feb 10, 2016

I'm setting up a Consul cluster from 3 node for evaluation purposes using version 0.6.3.

Here is my configuration:

{
    "acl_datacenter": "main-dc",
    "acl_default_policy": "deny",
    "acl_master_token": "secret-of-consul",

    "bootstrap_expect": 3,
    "bind_addr": "192.168.1.10",

    "client_addr": "192.168.1.10",

    "encrypt": "value-removed",

    "datacenter": "main-dc",
    "data_dir": "/var/data/consul",
    "domain": "internal.",

    "log_level": "trace",

    "rejoin_after_leave": true,
    "retry_join": ["192.168.1.11", "192.168.1.12"]

    "server": true,

    "ui": true,
    "ui_dir": "/opt/consul/current/var/data/web-ui",
}

The only different thing is obviously bind_addr and client_addr.
I'm using ui_dir because of issue #1071.

Now if I open private window in my browser and go to UI I can deregister any node.
It's a bug or a feature? :) I'd like to disallow de-registering of node by anonymous.

@slackpad
Copy link
Contributor

Hi @ashald thanks for opening an issue. This is indeed a "feature" in the current versions of Consul and we've got an open issue to add an ACL to protect this - #1383.

@ashald
Copy link
Contributor Author

ashald commented Feb 10, 2016

Thanks for quick reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants