In a secure, multi-tenant cluster, the operator doesn't want to give every user access to read or modify cluster state/config, nor to perform administrative actions. As such, we need to make sure that all such endpoints are authenticated and authorized.
We've already added authorization to some operator endpoints (/teardown, /reserve, etc.), but many remain unsecured.
- /roles, /observe, /registrar, /state-summary
- /maintenance, /machine,
- /logging, /profiler, /metrics, /flags, /system/stats.json
- Leave open? /redirect, /health, /version
See http://mesos.apache.org/documentation/latest/endpoints/ for a more complete list. Some endpoints (e.g. state.json) will need a finer-grained authz.