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 acl: correctly resolve ACL roles within client cache. into release/1.4.x #14975

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

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

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


The client ACL cache was not accounting for tokens which included ACL role links. This change modifies the behaviour to resolve role links to policies. It will also now store ACL roles within the cache for quick lookup. The cache TTL is configurable in the same manner as policies or tokens.

Another small fix is included that takes into account the ACL token expiry time. This was not included, which meant tokens with expiry could be used past the expiry time, until they were GC'd.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/jrasell/client-acl-cache-roles/intensely-hot-chicken branch from 517a713 to 728a7f0 Compare October 20, 2022 07:37
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 68d344c into release/1.4.x Oct 20, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/jrasell/client-acl-cache-roles/intensely-hot-chicken branch October 20, 2022 07:37
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants