Skip to content

acl: a deleted ACL policy still shows when reading token it was assigned to #14074

Open
@jrasell

Description

@jrasell

Nomad version

Nomad v1.3.3 (428b2cd8014c48ee9eae23f02712b7219da16d30)

Operating system and Environment details

Tested locally on macOS using a development agent.

Issue

When an ACL policy is deleted that is referenced by an active ACL token, the ACL token CLI and API still details the linked policy.

Reproduction steps

  1. Run a development agent using the following config snippet to ensure ACLs are enabled:
acl {
  enabled = true
}
  1. Bootstrap the ACL system via the nomad acl boostrap command.

  2. Create an ACL policy using the example policy below via the nomad acl policy apply -token=<root_token> test <file_path>:

node {
  policy = "read"
}
  1. Create an ACL token referencing the policy created above via nomad acl token create -policy=test
  2. Delete the policy via nomad acl policy delete test
  3. Read the information regarding the created token using nomad acl token -token=<token_secret_id> self

Expected Result

The final read of the token shows no policies linked.

Actual Result

The delete policy still shows, which can be a little confusing when trying to understand why the token no longer works.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Needs Roadmapping

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions