-
Notifications
You must be signed in to change notification settings - Fork 881
audit: add support for APIKey creation and deletion (logins) #4538
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
Comments
@bpmct @coadler @sharkymark Making sure this is on everyone's radar. |
This was referenced Oct 13, 2022
I agree with the criteria. Should we consider this a |
@bpmct I think that term would be a lot clearer. |
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity. |
resolved by #5925 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should add audit logging support for APIKey creation and deletion. API Keys, aka session tokens created on login, should be an auditable resource.
An audit log should be generated when a user successfully logs in or out, either via the web UI or via the CLI.
We don't have to worry about audit support for long-lived token creation; that will be handled in this ticket.
Assumption: we don't have to worry about the update of session tokens, even though the table has an
updated_at
column. Creation and deletion (login and logout) should suffice.The text was updated successfully, but these errors were encountered: