-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Allow identity
mount to be tunable
#14723
Allow identity
mount to be tunable
#14723
Conversation
Hi there! Thanks for this contribution. I'll get some eyes on it, but please don't forget to add a changelog entry. Thanks! :) |
@hsimon-hashicorp thanks! changelog added in e9114b5a9 |
I happened to notice this, and wondered - is there any reason to keep the concept of an "untunable mount" at all? Lines 86 to 91 in 254d8da
Wanting to tune fields displayed in the audit logs for Just something to think about whilst people's thoughts are in this area. |
Hi @maxb , some mounts such as the identity mount are more sensitive than others. As such, we'd like to make these mounts as standardized as possible from environment to environment to reduce the chances of complicated bugs arising due to, say, tuning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ianferguson, thanks for submitting this PR!
Regarding the this particular change/request, I do agree that users should have the ability to change audit settings for identity if they so choose. However, I'm unclear about the repercussions of tuning the other parameters for this mount. Would you please update this PR in such a way that only a subset of the tunable parameters can be submitted for certain mounts (like the identity mount)?
@HridoyRoy just getting back to this now Reading the mount tuning table on Vault v1.11.1 several of the tuning values are already set by default:
looking at the secrets mount tuning parameters they all seem like they'd have non-catastrophic and reasonable behaviors when set I tested tuning all possible values on a build of this branch:
and at least a few entity create/lookup type commands all worked fine before and after those tuning settings. I think it should be safe for the |
@HridoyRoy would you or someone else be able to review my last response? #14723 (comment) |
Hey there @ianferguson ! I'm sorry this languished a little without eyes on it. I've been exploring the code/area and I think this makes sense to merge. I appreciate your comment illustrating all of the options, too! Before we can merge it, you'll need to pull main into your branch, and there'll be a conflict I think, but an easy one (the line you're removing got renamed to I really appreciate your patience, and I'm sorry this waited for so long. I'm eager to see this one over the finish line to the end, though, so rest assured that your efforts won't be in vain. |
e9114b5
to
42d55e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Thanks for being so patient, and for responding to the feedback. I'm sorry this one took so long and slipped through the cracks a little, but I'm super eager to get this merged and I'm really glad we could get this in finally.
@VioletHynes thanks for merging so quickly, I was waiting for tests to pass before pinging you! |
resolves #14696
I didn't expect this to be so simple, but it seems like removing
identity
from the "non tunable" mounts list just works, at least for the audit hmac tuning I've tested.There may be other impacts I'm not aware of due to this, if y'all can think of any you want me to test for specifically please let me know, I'm happy to do so
Testing
Setup
I built my branch locally and started a Vault test server
Execution
In another shell I ran the follow commands to enable audit logs, write some groups, tune identity to allow the
name
field to be printed in plaintext in audit logs, and then write some groups again:Results: How that looked in the audit logs
Before tuning (
name
in request/response is hmac'd)After tuning (
name
is printed in plaintext`):