You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created an ACL Policy to allow Job operators to "list" and "read" all secrets under the path nomad/jobs. However that ACL policy seems to have no effect as these secrets are still not visible to the user with a token from this policy.
Hi @mr-karan and thanks for raising this issue. Whilst I could reproduce this behaviour in v1.4.1, running the same test against v1.4.2 did not produce the same error. I believe this bug was fixed as part of the work conducted for #15012. Would you be able to test you reproduction with v1.4.2?
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Output from
nomad version
1.4.1
Issue
I've created an ACL Policy to allow Job operators to "list" and "read" all secrets under the path
nomad/jobs
. However that ACL policy seems to have no effect as these secrets are still not visible to the user with a token from this policy.Reproduction steps
I've created an ACL Policy for job operators:
Expected Result
The above policy is for
dev
namespace and it should allow listing and reading all variables insidenomad/jobs
path.Actual Result
However, on opening the UI as a job operator with that policy, I only see this:
v/s with a management token:
The text was updated successfully, but these errors were encountered: