feat: Logins log for Fail2Ban

[berry-13]

I'm not sure if this is the function that was requested, which is why I welcome ideas on how to improve it. Every time a login fails, the logs are both displayed in the console and saved in the root folder in a file named login-logs.txt #985

logs:

{"level":"error","message":"Passport Local Strategy - Password does not match","parameters":[{"name":"isMatch","value":false}],"timestamp":"2023-09-23T23:24:38.786Z"}
{"level":"error","message":"[Login] [Login failed] [Username: myemail@test.com] [Request-IP: 45.xx.xx.238]","timestamp":"2023-09-23T23:24:38.786Z"}

Change Type

• New feature (non-breaking change which adds functionality)

Testing

check if the log and the .txt works properly

Test Configuration:

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes
• Any changes dependent on mine have been merged and published in downstream modules.

[XHyperDEVX]

it works, but... the log works if you enter wrong logical data. e.g. username: 123@456.com password: 123456789
but with wrong non logical data, like username: 123 password: 123 [which doesn't work because the username has to be an email and the password has to be min. 8 characters long] it won't be logged! i think that would be important to add.

[XHyperDEVX]

here e.g. /logins/login-logs.txt instead of just login-logs.txt
-> for better handling when using logrotate

[berry-13]

I know, I did it on purpose this way! I thought the logs would help you understand if someone wanted to attempt to brute force the password, etc..

[XHyperDEVX]

I know, I did it on purpose this way! I thought the logs would help you understand if someone wanted to attempt to brute force the password, etc..

No, the wish was to make librechat compatible with fail2ban xD

[danny-avila]

it works, but... the log works if you enter wrong logical data. e.g. username: 123@456.com password: 123456789 but with wrong non logical data, like username: 123 password: 123 [which doesn't work because the username has to be an email and the password has to be min. 8 characters long] it won't be logged! i think that would be important to add.

this is a good point, it should count as a login fail when the validation fails @berry-13