We have a login message for failed login attempts, but no counterpart for successful login attempts.
It should include username, and IP address/host, as with the failed attempts.
Originally created by @RomanHargrave on GitHub (Nov 20, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/264
We have a login message for failed login attempts, but no counterpart for successful login attempts.
It should include username, and IP address/host, as with the failed attempts.
I'm guessing the rocket-0.4 branch would be the best place for this due to rocket logging features added in 2fde4e6?
<!-- gh-comment-id:446062993 -->
@Algebro7 commented on GitHub (Dec 11, 2018):
I'm guessing the rocket-0.4 branch would be the best place for this due to rocket logging features added in 2fde4e6?
Yes, that branch is probably going to be merged sometime this week, so it's probably the best place to make changes to.
<!-- gh-comment-id:446194304 -->
@dani-garcia commented on GitHub (Dec 11, 2018):
Yes, that branch is probably going to be merged sometime this week, so it's probably the best place to make changes to.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @RomanHargrave on GitHub (Nov 20, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/264
We have a login message for failed login attempts, but no counterpart for successful login attempts.
It should include username, and IP address/host, as with the failed attempts.
@mprasil commented on GitHub (Nov 20, 2018):
This should be fairly easy to add.
@RomanHargrave commented on GitHub (Nov 20, 2018):
I'll probably get it when I get home.
@Algebro7 commented on GitHub (Dec 11, 2018):
I'm guessing the rocket-0.4 branch would be the best place for this due to rocket logging features added in 2fde4e6?
@dani-garcia commented on GitHub (Dec 11, 2018):
Yes, that branch is probably going to be merged sometime this week, so it's probably the best place to make changes to.
@mprasil commented on GitHub (Dec 11, 2018):
This is in latest beta, I think we can now close this.