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

Backport of UI: Correctly call resultant-acl endpoint when user root is root into release/1.15.x #25785

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #25766 to be assessed for backporting due to the inclusion of the label backport/1.15.x.

The below text is copied from the body of the original PR.


In #25256 we updated the permissions adapter logic to call the resultant-acl endpoint with the user's namespace, if it exists. However, the logic did not work for users in the root namespace who log into a child namespace. Now it does, with test coverage.


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/ui/user-root-permissions/explicitly-enhanced-corgi branch from 5fd7e5d to 0048468 Compare March 5, 2024 17:36
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Mar 5, 2024
Copy link

github-actions bot commented Mar 5, 2024

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Mar 5, 2024

CI Results:
All Go tests succeeded! ✅

@hashishaw hashishaw added this to the 1.15.7 milestone Mar 7, 2024
@hashishaw hashishaw merged commit 6364acb into release/1.15.x Mar 7, 2024
27 of 29 checks passed
@hashishaw hashishaw deleted the backport/ui/user-root-permissions/explicitly-enhanced-corgi branch March 7, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants