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

Secure actuator endpoints behind a specific /management URL #3550

Closed
jdubois opened this issue May 6, 2016 · 1 comment
Closed

Secure actuator endpoints behind a specific /management URL #3550

jdubois opened this issue May 6, 2016 · 1 comment
Milestone

Comments

@jdubois
Copy link
Member

jdubois commented May 6, 2016

This is quite urgent, sorry to break stuff at the last minute, but it's for security.

This has already been discussed (ping @cbornet @gmarziou I think you participated), but we have an issue with our actuator endpoints:

  • We have a lot of them secured in the SecurityConfiguration, and that makes a long file (and besides it has a small performance cost as Spring Security needs to go thru all of them)
  • It's not fully secured as when Spring Boot Actuator adds more endpoints we might forget to update them (and there's probably already a security issue here today!!)
  • Microservices are not secured, as they were supposed to be behind the gateway: in fact that's false in several cases, for example with Heroku, where all services are publicly available. So another big security issue.

My proposal, and I'm going to work on this ASAP (as it's security-related):

  • Put all endpoints behind "/management" so it's easy to secure them with just one Spring Security rule
  • (optional) Add basic auth support for them, so that the JHipster Registry (or any other tool) can access them remotely easily
jdubois added a commit to jhipster/jhipster-registry that referenced this issue May 6, 2016
@jdubois jdubois closed this as completed in bd09d3b May 6, 2016
@gmarziou
Copy link
Contributor

gmarziou commented May 6, 2016

I am all for name spacing apis, so +1

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