-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Only allow access request deletion through static roles' permissions #9540
Conversation
@russjones after this change the web UI will still allow the user to click the "delete" button on the access request if an elevated role would allow it, displaying an error message after confirmation. The code that ultimately decides what operations are shown as available to the user ( |
8e1ce99
to
55d4347
Compare
@espadolini Please add test coverage to this PR. |
e92771a
to
3a254df
Compare
3a254df
to
d18f9d1
Compare
d18f9d1
to
877b815
Compare
877b815
to
d8a482c
Compare
@russjones which backports, if any? |
Access request deletion is not meant to be used on a regular basis, and in fact it's not an operation that
tsh
supports; it's however supported via gRPC and the web interface. Letting a temporarily privileged user delete access requests can lead to reduced visibility over the action of the user, and can cause confusion if the cert authority needs to reference that access request to issue more certificates for other purposes.This partially mitigates TEL-Q321-8.