-
Notifications
You must be signed in to change notification settings - Fork 647
BSC audit log record must contain login #2302
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
Labels
area/blobstorage
BlobStorage issues
Comments
This was referenced May 7, 2024
robot-piglet
pushed a commit
that referenced
this issue
May 27, 2024
…2302 8f4800b43ba453e815c1148a0197c819a13763ca
robot-piglet
pushed a commit
that referenced
this issue
Jun 4, 2024
…s version is used.. #2302 0843dd6fab7789634d13bdde50586f8d122288fa
Merged
This was referenced Jun 11, 2024
Merged
This was referenced Jun 14, 2024
This was referenced Jun 15, 2024
Closed
Merged
This was referenced Jun 19, 2024
This was referenced Jun 23, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It was discovered that some records in blob storage controller audit log don't contain login info of a user who initiated a request.
It's important to always in every possible case to log login of a user, who initiated a request to the system that caused changes in BSC.
DoD:
The text was updated successfully, but these errors were encountered: