We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Original comment by @jakommo:
On https://www.elastic.co/guide/en/x-pack/5.6/auditing.html#audit-event-attributes under "Table 14. REST authentication_success Attributes" we list:
But the logs lines look like:
[2017-09-19T10:13:47,339] [rest] [authentication_success] principal=[kibana], realm=[reserved], uri=[/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip], params=[{filter_path=nodes.*.version,nodes.*.http.publish_address,nodes.*.ip}] [2017-09-19T10:13:47,342] [rest] [authentication_success] principal=[kibana], realm=[reserved], uri=[/_cluster/health/.monitoring-*-2-*%2C.monitoring-*-6-*?timeout=5s], params=[{index=.monitoring-*-2-*,.monitoring-*-6-*, timeout=5s}] [2017-09-19T10:13:47,522] [rest] [authentication_success] principal=[kibana], realm=[reserved], uri=[/.reporting-*/esqueue/_search?version=true], params=[{index=.reporting-*, type=esqueue, version=true}]
It seems to use principal rather than user.
principal
user
The text was updated successfully, but these errors were encountered:
belatedly resolved by #35510
Sorry, something went wrong.
albertzaharovits
No branches or pull requests
Original comment by @jakommo:
On https://www.elastic.co/guide/en/x-pack/5.6/auditing.html#audit-event-attributes under "Table 14. REST authentication_success Attributes" we list:
But the logs lines look like:
It seems to use
principal
rather thanuser
.The text was updated successfully, but these errors were encountered: