Skip to content

[fix] restrict the actuator endpoints to admin - #4277

Open
Duansg wants to merge 2 commits into
apache:masterfrom
Duansg:fix-actuator-authz
Open

[fix] restrict the actuator endpoints to admin#4277
Duansg wants to merge 2 commits into
apache:masterfrom
Duansg:fix-actuator-authz

Conversation

@Duansg

@Duansg Duansg commented Jul 29, 2026

Copy link
Copy Markdown
Member

What's changed?

Add role rules for /actuator/**, restricting them to admin.

Checklist

  • I have read the Contributing Guide
  • I have written the necessary doc or comment.
  • I have added the necessary unit tests and all cases have passed.

Add or update API

  • I have added the necessary e2e tests and all cases have passed.

@zqr10159

Copy link
Copy Markdown
Member

Several compose/script Sureness files add /actuator/**===get===[admin] inside excludedResource. A resource listed there can bypass authentication before resourceRole is applied, so those distributions may remain exposed. Please move the rule into resourceRole consistently, assert that actuator paths are absent from every exclusion list, and add 401/403/admin-success tests across the packaged configurations. This PR also does not protect the collector management/Prometheus endpoint; that endpoint needs a separate bind/auth control.

The rule was added under `excludedResource` in all six shipped copies, where
the format is `api===method`. A three segment line there never matches a
request, so every container deployment kept serving `/actuator/**` with no
role requirement at all and the fix only took effect for the startup jar.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants