Originally created by @TMHBOFH on GitHub (May 26, 2018).
Hi,
at first thanks for your great work on this project.
I get an "An unexpected error has occurred" if would like enable 2FA.
I use this docker image with Web Vault (version 1.26.0)
the log show
POST /api/two-factor/authenticator application/json; charset=utf-8:
=> Matched: POST /api/two-factor/authenticator
=> Error: Couldn't parse JSON body: Error("invalid type: string "731025", expected u64", line: 1, column: 17)
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
best regards
Originally created by @TMHBOFH on GitHub (May 26, 2018).
Hi,
at first thanks for your great work on this project.
I get an "An unexpected error has occurred" if would like enable 2FA.
I use [this docker image](https://github.com/mprasil/bitwarden_rs) with Web Vault (version 1.26.0)
the log show
POST /api/two-factor/authenticator application/json; charset=utf-8:
=> Matched: POST /api/two-factor/authenticator
=> Error: Couldn't parse JSON body: Error("invalid type: string "731025", expected u64", line: 1, column: 17)
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
best regards
The official server doesn't seem to care about uppercase or lowercase, or about strings or numbers, so it seems like a conscious design choice by the author. I don't think there is a need to open an issue about it.
@dani-garcia commented on GitHub (May 26, 2018):
The official server doesn't seem to care about uppercase or lowercase, or about strings or numbers, so it seems like a conscious design choice by the author. I don't think there is a need to open an issue about it.
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 @TMHBOFH on GitHub (May 26, 2018).
Hi,
at first thanks for your great work on this project.
I get an "An unexpected error has occurred" if would like enable 2FA.
I use this docker image with Web Vault (version 1.26.0)
the log show
POST /api/two-factor/authenticator application/json; charset=utf-8:
=> Matched: POST /api/two-factor/authenticator
=> Error: Couldn't parse JSON body: Error("invalid type: string "731025", expected u64", line: 1, column: 17)
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
best regards
@dani-garcia commented on GitHub (May 26, 2018):
Thanks, the clients sometimes send numbers or strings. This should be fixed now.
@TMHBOFH commented on GitHub (May 26, 2018):
Thanks for your fast reply.
Should i open an issue on Web Vault?
@dani-garcia commented on GitHub (May 26, 2018):
The official server doesn't seem to care about uppercase or lowercase, or about strings or numbers, so it seems like a conscious design choice by the author. I don't think there is a need to open an issue about it.
@TMHBOFH commented on GitHub (May 26, 2018):
ok Thanks for your help