bitwarden/help
1
0
Fork 0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Code Issues Releases Wiki Activity
Files
master
help/_articles/hosting/configure-clients.md
fred_the_tech_writer 5e11a4ac9b Meta-Descriptions (#778) 
* initial commit

* 2nd batch

* last batch
2021-10-27 10:38:41 -04:00

4.0 KiB
Raw Permalink Blame History

layout, title, categories, featured, popular, tags, order, description
layout title categories featured popular tags order description
article Configure Clients Centrally
hosting
true false
11 This article explains how to centrally configure client applications settings to connect to your self-hosted server.

When operating a self-hosted Bitwarden server in a business setting, administrators may want to centrally configure client application settings (particularly, Server URL) before deploying to users with an endpoint management platform.

The process for doing so will be different for each client application:

{% capture mobile_info %}

Mobile

Most Mobile Device Management (MDM) or Enterprise Mobility Management (EMM) solutions allow administrators to pre-configure applications before deployment in a standard fashion. To pre-configure Bitwarden Mobile apps to use your self-hosted Server URL, construct the following Application Configuration:

Configuration Key Value Type Configuration Value
baseEnvironmentUrl string Your self-hosted Server URL, for example https://my.bitwarden.server.com.

{% endcapture %} {{ mobile_info | markdownify}}

{% capture desktop_info %}

Desktop

To centrally configure the Desktop app for deployment, first complete the following steps on a single workstation:

  1. Install the Desktop app. If you're using Windows, silent install Bitwarden using installer.exe /S (see NSIS documentation{:target="_blank"}).

  2. Navigate to the Desktop app's locally stored settings. This directory is different depending on your OS (e.g. %AppData%\Bitwarden on Windows, ~/Library/Application Support/Bitwarden on macOS). Find your directory.

  3. In the directory, open the data.json file.

  4. Edit data.json to configure the Desktop app as desired. In particular, create the following object to configure the app with your self-hosted Server URL:

} "environmentUrls": { "base": "https://my.bitwarden.server.com", "api": null, "identity": null, "webVault": null, "icons": null, "notifications": null, "events": null, "enterprise": null } }

5. Once configured the way you want it, use your endpoint management solution of choice (like [Jamf](https://www.jamf.com/){:target="\_blank"}) to deploy the pre-configured Desktop app as a template.

{% endcapture %}
{{ desktop_info | markdownify}}
</div>
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
{% capture browser_extension %}

#### Browser Extensions

While it is possible to deploy Bitwarden Browser Extensions using an endpoint management solution like [Jamf](https://www.jamf.com/){:target="\_blank"} or Microsoft Endpoint Manager (formerly SCCM), it is currently **not possible** to alter the configuration in this way.

Instruct your end-users to follow [these steps]({{site.baseurl}}/article/change-client-environment/#browser-extensions-desktop-apps-and-mobile-apps) to connect a Browser Extension to your self-hosted server.

{% endcapture %}
{{ browser_extension | markdownify}}
</div>
</div>