Skip to content

[8.2] Ignore app priv failures when resolving superuser (#85519) #85587

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

Merged
merged 1 commit into from
Apr 1, 2022

Conversation

tvernum
Copy link
Contributor

@tvernum tvernum commented Apr 1, 2022

Backports the following commits to 8.2:

In elastic#81400 we changed `superuser` to no longer have _every_ privilege.
Consequently, we also removed the special case code that existed that
would ignore all other roles for any user that had superuser role.

However, we added some special handling so that failing to resolve those
other roles would not block superuser access - when a user has superuser
role, any failures in role resolution will be effectively ignored, and
the user will be given the superuser role only.

However, this failure handling did not account for the loading of
application privileges. If application privileges needed to be loaded,
but failed, this could prevent resolution of the superuser role.

This change extends the failure handling to encompass the full
resolution of roles, and fallback to superuser only, whenever other
roles or application privileges are unavailable

Relates: elastic#85312
@tvernum tvernum added auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport labels Apr 1, 2022
@elasticsearchmachine elasticsearchmachine merged commit ccfc925 into elastic:8.2 Apr 1, 2022
@tvernum tvernum deleted the backport/8.2/pr-85519 branch April 1, 2022 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.2.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants