-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Changed log level for message with authz opt out #199678
Changed log level for message with authz opt out #199678
Conversation
Pinging @elastic/kibana-security (Team:Security) |
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.
Using debug
level will prevent spamming the logs by default.
Thank you!
LGTM
@@ -48,7 +48,7 @@ export function initAPIAuthorization( | |||
|
|||
if (security) { | |||
if (isAuthzDisabled(security.authz)) { | |||
logger.warn( | |||
logger.debug( |
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.
question: Is there any value in this log entry at all? I mean, we already have HTTP logs if we want to know which endpoint is being called, and if we want to check whether this endpoint has authorization enabled or disabled, we just need to know the Kibana version, since the definition is mostly static and set in the code.
If, for some reason, we want to keep this as a debug log, it would make sense to remove the request.url.search
part, as it’s not relevant to the authorization decision (it's essentially based on path
) and might potentially contain sensitive data that we don’t want to record in logs.
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.
tbh I think we are okay to delete it, don't see any issues with that, we are just generating additional noise with it
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.
removed in 4493b87
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.
Thanks!
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]
History
|
@elasticmachine merge upstream |
Starting backport for target branches: 8.x |
## Summary Changed log level for message with authz opt out from `warn` to `debug` __Closes: https://github.com/elastic/kibana/issues/199677__ (cherry picked from commit 9bb3661)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
## Summary Changed log level for message with authz opt out from `warn` to `debug` __Closes: https://github.com/elastic/kibana/issues/199677__
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Summary
Changed log level for message with authz opt out from
warn
todebug
Closes: #199677