You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Event logs show cli user "Logged in"
Event logs show cli user "Viewed password for item fasdfadfd"
Actual Result
Event logs show cli user "Logged in"
Does not record that the password was viewed.
On a probably related issue. When I perform the "bw get password item" when it returns the item password it also says: "Event Post Failed"
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows, macOS, Linux
Operating System Version
No response
Shell
Bash, Zsh, PowerShell
Build Version
2024.8.2
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Thank you for this report. I was able to reproduce this and have flagged it to the Engineering department.
Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.
By the way, are you seeing 1107 (Viewed Item) events for the relevant vault item, after running bw get password <item id>? Also, on which operating system did you test this?
Steps To Reproduce
Expected Result
Event logs show cli user "Logged in"
Event logs show cli user "Viewed password for item fasdfadfd"
Actual Result
Event logs show cli user "Logged in"
Does not record that the password was viewed.
On a probably related issue. When I perform the "bw get password item" when it returns the item password it also says: "Event Post Failed"
Screenshots or Videos
No response
Additional Context
No response
Operating System
Windows, macOS, Linux
Operating System Version
No response
Shell
Bash, Zsh, PowerShell
Build Version
2024.8.2
Issue Tracking Info
The text was updated successfully, but these errors were encountered: