[FIXED] Safari plugin calling /api/accounts/verify-password

Help
1

It looks as though a recent change in the Safari BW plugin has vault unlock requests going to the vault server, doing a POST to /api/accounts/verify-password that results in a 404. Other plugins work fine as well as the desktop client. (all latest versions)

Anyone else seeing this behavior?

2

Could you check which version you are using?
I just tested it with the latest desktop app (v1.22.1) which has the extension version v1.46.1. i tested locking, unlocking, logout, login and nothing strange happened.

3

Same versions as you. 1.22.1, extension 1.46.1. Logging out/in a few times seemed to fix this, oddly. Here’s the log showing the last couple of attempts, finally one that worked. Most strange! Thanks for the quick reply (and for your hard work on the project)

[2020-09-24 19:55:32.146][request][INFO] POST /api/accounts/verify-password
[2020-09-24 19:55:32.146][response][INFO] 404 Not Found
[2020-09-24 19:55:43.257][request][INFO] POST /api/accounts/verify-password
[2020-09-24 19:55:43.257][response][INFO] 404 Not Found
[2020-09-24 19:55:52.699][request][INFO] POST /api/accounts/prelogin
[2020-09-24 19:55:52.699][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK
[2020-09-24 19:55:52.743][request][INFO] POST /identity/connect/token
[2020-09-24 19:55:52.808][bitwarden_rs::api::identity][INFO] User x logged in successfully. IP: x
4

Hello @moocow,
It took a bit of research, but i found a way to trigger this my self.
I already created a ticket for this: https://github.com/dani-garcia/bitwarden_rs/issues/1156

I will also see if i can solve this quickly.

Thanks for reporting.

5

Well, i also have fixed it already.
We now have to wait for the PR to be merged and the docker images to be build.

Though, this was a very strange corner case, since i would not know how you could trigger this without using some kind of clean-tool like CCLeaner or BleachBit maybe.

6

Yeah - it’s really strange. I don’t have any apps that would have tampered with the functionality or the system in a way that would have caused this; it just happened out of the blue. The only thing that I can think might have caused it is a Safari upgrade that happened a couple of days ago to 14.0 (15610.1.28.1.9, 15610). Thanks for looking into this and for the PR as well. :+1:

7

The latest testing build on docker hub should have this fix in it already.