9e3f1581fb
ACL tokens can now utilize ACL roles in order to provide API authorization. Each ACL token can be created and linked to an array of policies as well as an array of ACL role links. The link can be provided via the role name or ID, but internally, is always resolved to the ID as this is immutable whereas the name can be changed by operators. When resolving an ACL token, the policies linked from an ACL role are unpacked and combined with the policy array to form the complete auth set for the token. The ACL token creation endpoint handles deduplicating ACL role links as well as ensuring they exist within state. When reading a token, Nomad will also ensure the ACL role link is current. This handles ACL roles being deleted from under a token from a UX standpoint. |
||
---|---|---|
.. | ||
indexer | ||
paginator | ||
autopilot.go | ||
autopilot_test.go | ||
deployment_events_test.go | ||
events.go | ||
events_test.go | ||
iterator.go | ||
schema.go | ||
schema_test.go | ||
state_changes.go | ||
state_store.go | ||
state_store_acl.go | ||
state_store_acl_test.go | ||
state_store_oss.go | ||
state_store_restore.go | ||
state_store_restore_test.go | ||
state_store_secure_variables.go | ||
state_store_secure_variables_test.go | ||
state_store_service_regisration_test.go | ||
state_store_service_registration.go | ||
state_store_test.go | ||
testing.go |