-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Authc] Security authentication config #205367
[Authc] Security authentication config #205367
Conversation
Pinging @elastic/kibana-security (Team:Security) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
883da44
to
b682613
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good and makes sense to me. Left a non blocker comment, but I'd like to get your thoughts before merging!
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
The CI Stats report is too large to be displayed here, check out the CI build annotation for this information. History
|
Starting backport for target branches: 8.x |
## Summary We cannot support `security.authc` evolvement for versioned routes, since authentication is passed down to hapi during route registration and it is tight up with the authentication strategy defined. Adjusted the code to pass `auth` option correctly. https://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios __Fixes: https://github.com/elastic/kibana/issues/205360__ (cherry picked from commit 26cc597)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.x`: - [[Authc] Security authentication config (#205367)](#205367) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-06T16:02:21Z","message":"[Authc] Security authentication config (#205367)\n\n## Summary\r\n\r\nWe cannot support `security.authc` evolvement for versioned routes,\r\nsince authentication is passed down to hapi during route registration\r\nand it is tight up with the authentication strategy defined. Adjusted\r\nthe code to pass `auth` option correctly.\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n__Fixes: https://github.com/elastic/kibana/issues/205360__","sha":"26cc597b368d21df305fc3a3c84e0bb94e8e8881","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","Feature:Security/Authentication","release_note:skip","v9.0.0","backport:prev-minor"],"title":"[Authc] Security authentication config","number":205367,"url":"https://github.com/elastic/kibana/pull/205367","mergeCommit":{"message":"[Authc] Security authentication config (#205367)\n\n## Summary\r\n\r\nWe cannot support `security.authc` evolvement for versioned routes,\r\nsince authentication is passed down to hapi during route registration\r\nand it is tight up with the authentication strategy defined. Adjusted\r\nthe code to pass `auth` option correctly.\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n__Fixes: https://github.com/elastic/kibana/issues/205360__","sha":"26cc597b368d21df305fc3a3c84e0bb94e8e8881"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205367","number":205367,"mergeCommit":{"message":"[Authc] Security authentication config (#205367)\n\n## Summary\r\n\r\nWe cannot support `security.authc` evolvement for versioned routes,\r\nsince authentication is passed down to hapi during route registration\r\nand it is tight up with the authentication strategy defined. Adjusted\r\nthe code to pass `auth` option correctly.\r\n\r\n\r\nhttps://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393\r\n\r\n\r\n### Checklist\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n__Fixes: https://github.com/elastic/kibana/issues/205360__","sha":"26cc597b368d21df305fc3a3c84e0bb94e8e8881"}}]}] BACKPORT--> Co-authored-by: Elena Shostak <[email protected]>
## Summary We cannot support `security.authc` evolvement for versioned routes, since authentication is passed down to hapi during route registration and it is tight up with the authentication strategy defined. Adjusted the code to pass `auth` option correctly. https://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios __Fixes: https://github.com/elastic/kibana/issues/205360__
## Summary We cannot support `security.authc` evolvement for versioned routes, since authentication is passed down to hapi during route registration and it is tight up with the authentication strategy defined. Adjusted the code to pass `auth` option correctly. https://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios __Fixes: https://github.com/elastic/kibana/issues/205360__
## Summary We cannot support `security.authc` evolvement for versioned routes, since authentication is passed down to hapi during route registration and it is tight up with the authentication strategy defined. Adjusted the code to pass `auth` option correctly. https://github.com/elastic/kibana/blob/e5cf28bc27b6ca80c92c44a4fc805adce857b518/packages/core/http/core-http-server-internal/src/http_server.ts#L378-L393 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios __Fixes: https://github.com/elastic/kibana/issues/205360__
Summary
We cannot support
security.authc
evolvement for versioned routes, since authentication is passed down to hapi during route registration and it is tight up with the authentication strategy defined. Adjusted the code to passauth
option correctly.kibana/packages/core/http/core-http-server-internal/src/http_server.ts
Lines 378 to 393 in e5cf28b
Checklist
Fixes: #205360