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
Is your feature request related to a problem? Please describe.
There is a clear demand to template policies based on token metadata. Currently, there is no way to do so, because of potential security risks of child tokens changing their metadata and walking around policies.
fixed_metadata "sticks" to all child non-orphan tokens, and whenever that key is set to true, the token is refused write access to token metadata.
Another option would be additional field in tokens, called fixed_metadata. We can create "fixed" metadata with one of the following:
sudo or root access to the auth/token/create and setting fixed_metadata parameter to the metadata we want to fix to the token.
Access to the auth/token/create/:role that has fix_metadata set to true, and setting fixed_metadata to the metadata we want to fix to the token.
Same as the previous option, fixed_metadata "sticks" to all child non-orphan tokens.
Describe alternatives you've considered
Multiple AppRoles. While that works, it limits flexibility a lot, because we have a generic model of where we put secrets for different apps, and keeping track of that in terraform is very verbose. All we want is the following policy:
Is your feature request related to a problem? Please describe.
There is a clear demand to template policies based on token metadata. Currently, there is no way to do so, because of potential security risks of child tokens changing their metadata and walking around policies.
Here's an example issue: #10460
Describe the solution you'd like
The solution could work analogously to orphan tokens. I have 2 possible options:
We can create "fixed" metadata with one the following:
sudo
orroot
access to theauth/token/create
and settingfixed_metadata
parameter to true.auth/token/create/:role
that hasfix_metadata
set.Then policies may template
{{ token.metadata }}
, if and only iffixed_metadata
is set to true. Pseudocode of how this would be handled in code:fixed_metadata
"sticks" to all child non-orphan tokens, and whenever that key is set to true, the token is refused write access to token metadata.Another option would be additional field in tokens, called
fixed_metadata
. We can create "fixed" metadata with one of the following:sudo
orroot
access to theauth/token/create
and settingfixed_metadata
parameter to the metadata we want to fix to the token.auth/token/create/:role
that hasfix_metadata
set to true, and settingfixed_metadata
to the metadata we want to fix to the token.Same as the previous option,
fixed_metadata
"sticks" to all child non-orphan tokens.Describe alternatives you've considered
Multiple AppRoles. While that works, it limits flexibility a lot, because we have a generic model of where we put secrets for different apps, and keeping track of that in terraform is very verbose. All we want is the following policy:
The text was updated successfully, but these errors were encountered: