Skip to content
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 email & username to audit logs records #4158

Open
dmitryroshchin opened this issue Dec 14, 2023 · 2 comments
Open

add email & username to audit logs records #4158

dmitryroshchin opened this issue Dec 14, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@dmitryroshchin
Copy link

Is your feature request related to a problem? Please describe.
Audit log records of every system should help administrators to answer the following questions:
Who did what and when?
Boundary audit logs do provide this info, but there is no convenient way for analyzing it, because the only field in auth.userinfo record is id.

    "auth": {
      "auth_token_id": "",
      "user_info": {
        "id": "u_Qifo7VLXaA",
     }

Some kind of additional lookups required of translate it to human readable form.

Describe the solution you'd like
email and full_name fields should be added to auth.user_info audit records, like in the following example:

    "auth": {
      "auth_token_id": "",
      "user_info": {
        "id": "u_Qifo7VLXaA",
        "email": "user@examaple.com",
        "full_name": "example user" 
      }

Additional context
We're using OIDC auth method.
Here is the discussion of the issue
https://discuss.hashicorp.com/t/email-and-username-in-audit-logs/60147

@dmitryroshchin dmitryroshchin added the enhancement New feature or request label Dec 14, 2023
@dmitryroshchin
Copy link
Author

calling @jimlambrt

@anando-chatterjee
Copy link

Hi @dmitryroshchin thanks for logging this feature request. As discussed in the other thread, Boundary's audit log does contain details of the user performing any authenticated actions - just not additional bits such as email etc. We don't have plans to implement this functionality in the near future since a viable workaround exists, however I will keep this request open in order for other community members to weigh in and provide their upvotes. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants