Invalid Login Error Code #317

New issue

Closed

opened 2026-02-20 08:01:20 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 08:01:20 -05:00

Owner

Originally created by @uchagani on GitHub (Jun 9, 2019).

Is there a reason bitwarden_rs returns a 400 instead of a 401 or 403 when invalid credentials are entered?

Originally created by @uchagani on GitHub (Jun 9, 2019). Is there a reason bitwarden_rs returns a `400` instead of a `401` or `403` when invalid credentials are entered?

deekerman closed this issue

2026-02-20 08:01:20 -05:00

deekerman commented

2026-02-20 08:01:21 -05:00

Author

Owner

@mprasil commented on GitHub (Jun 10, 2019):

I believe upstream API implementation also returns 400 or is that not the case?

@mprasil commented on GitHub (Jun 10, 2019): I believe upstream API implementation also returns `400` or is that not the case?

deekerman commented

2026-02-20 08:01:21 -05:00

Author

Owner

@uchagani commented on GitHub (Jun 10, 2019):

Not sure tbh. I was just trying to use fail2ban at the reverse proxy layer and saw the 400. I just figured a 403 error would be a more accurate error to look for in the logs.

@uchagani commented on GitHub (Jun 10, 2019): Not sure tbh. I was just trying to use fail2ban at the reverse proxy layer and saw the 400. I just figured a 403 error would be a more accurate error to look for in the logs.

deekerman commented

2026-02-20 08:01:21 -05:00

Author

Owner

@mprasil commented on GitHub (Jun 10, 2019):

Just checked and upstream does return 400, so we need to do the same for compatibility reasons.

I'm going to close this now, feel free to reopen if there are any outstanding questions.

@mprasil commented on GitHub (Jun 10, 2019): Just checked and upstream does return `400`, so we need to do the same for compatibility reasons. I'm going to close this now, feel free to reopen if there are any outstanding questions.

deekerman referenced this issue

2026-02-20 08:03:42 -05:00

Unable to run bitwarden_rs with nginx and basic auth #605