Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

Vault 2.2.0 doesn't work in Chrome when self-hosted over unencrypted connection #254

Closed
mprasil opened this issue Aug 31, 2018 · 1 comment

Comments

@mprasil
Copy link

mprasil commented Aug 31, 2018

When Vault is self-hosted on unecrypted (HTTP) connection, users can't register or log in with Chrome. The Submit and Log In buttons don't work. I can see this error in console. This is only specific to Chrome/Chromium, I have tested it with version 68.0.3440.106. Vault works fine in Safari and Firefox. Some people also reported Edge working fine.

I'm not sure if this is appropriate place to report this as it came up as issue some of the bitwarden_rs users reported. I don't think it's specific to any API backend, but feel free to close, I just thought you might want to be aware. See linked issue for more info.

@kspearrin
Copy link
Member

You cannot run the web vault with http. Web crypto apis do not work without https. This is by design in the browser.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants