-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Add authenticating ID and user ID to request logging #24473
Labels
Comments
davidby-influx
added
kind/enhancement
area/2.x
OSS 2.0 related issues and PRs
team/edge
area/logging
labels
Nov 22, 2023
davidby-influx
added a commit
that referenced
this issue
Nov 22, 2023
To allow rudimentary security auditing of logs, add the authenticating ID and the user ID when possible to the request logs. When a request is authorized for V1 or V2 API, store the authorizer object to be used by the logger up the call stack. closes #24473
davidby-influx
changed the title
Add authenticating ID and user ID to request logging for Influxdb OSS 2.X
Add authenticating ID and user ID to request logging
Nov 22, 2023
davidby-influx
added a commit
that referenced
this issue
Nov 22, 2023
To allow rudimentary security auditing of logs, add the authenticating ID and the user ID when possible to the request logs. When a request is authorized for V1 or V2 API, store the authorizer object to be used by the logger up the call stack. closes #24473
davidby-influx
added a commit
that referenced
this issue
Nov 22, 2023
To allow rudimentary security auditing of logs, add the authenticating ID and the user ID when possible to the request logs. When a request is authorized for V1 or V2 API, store the authorizer object to be used by the logger up the call stack. closes #24473 (cherry picked from commit 13cf6be) closes #24475
davidby-influx
added a commit
that referenced
this issue
Nov 22, 2023
…24479) To allow rudimentary security auditing of logs, add the authenticating ID and the user ID when possible to the request logs. When a request is authorized for V1 or V2 API, store the authorizer object to be used by the logger up the call stack. closes #24473 (cherry picked from commit 13cf6be) closes #24475
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
To allow rudimentary security auditing of logs,
add the authenticating ID and the user ID when
possible to the request logs. When a request is
authorized for V1 or V2 API, store the authorizer
object to be used by the logger up the call stack.
The text was updated successfully, but these errors were encountered: