From ad2232b92f0a07ca4e5c533114c62915679cdad3 Mon Sep 17 00:00:00 2001 From: Dane Powell Date: Tue, 13 Jul 2021 12:04:39 -0700 Subject: [PATCH] [readme] enable desktop communication --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index efd335a231..722ab860f7 100644 --- a/README.md +++ b/README.md @@ -43,6 +43,14 @@ You can now load the extension into your browser through the browser's extension 1. Type `about:debugging` in your address bar to bring up the add-ons page. 2. Click the `Load Temporary Add-on` button, navigate to the `build/manifest.json` file, and "Open". +**Desktop communication** + +Native Messaging (communication between the desktop application and browser extension) works by having the browser start a lightweight proxy baked into our desktop application. + +Out of the box, the desktop application can only communicate with the production browser extension. When you enable browser integration in the desktop application, the application generates manifests which contain the production IDs of the browser extensions. To enable communication between the desktop application and development versions of browser extensions, add the development IDs to the `allowed_extensions` section of the corresponding manifests. + +Manifests are located in the `browser` subdirectory of the Bitwarden configuration directory. For instance, on Windows the manifests are located at `C:\Users\\AppData\Roaming\Bitwarden\browsers`. Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again. + # Contribute Code contributions are welcome! Please commit any pull requests against the `master` branch. Learn more about how to contribute by reading the [`CONTRIBUTING.md`](CONTRIBUTING.md) file.