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

Misc (#807)

Browse Source 
* tip - export format when uploading to a new account

* update on premise - cron example

* note on failed pin attempts

* strike email requirement for self-host licensing

* FAQ item on changing sp entity id, acs, callback path, etc.

* tips on --apikey for CLI in SSO required organizations

* issue 804
This commit is contained in:
fred_the_tech_writer
2021-11-17 10:50:42 -05:00
committed by GitHub
parent 4cb068e949
commit f32f7507d7
8 changed files with 43 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
_articles/hosting/licensing-on-premise.md
View File

@@ -48,13 +48,13 @@ You must be an [Organization Owner]({{site.baseurl}}/article/user-types-access-c
1. In the Cloud [Web Vault]({{site.baseurl}}/article/getting-started-webvault), open your Organization.
2. Select the Organization **Settings** tab and select **Subscription** from the left menu.
3. Select the **Download License** button.
4. When prompted, enter the installation id that was used to install your self-hosted server and select **Submit**.
4. When prompted, enter the installation ID that was used to install your self-hosted server and select **Submit**.
If you don't know the installation id off-hand, you can retrieve it from `./bwdata/env/global.override.env`.
If you don't know the installation ID off-hand, you can retrieve it from `./bwdata/env/global.override.env`.
#### Apply your License
1. Log in to your self-hosted Web Vault with an email address that matches the Cloud-hosted account from which you downloaded the license.
1. Log in to your self-hosted Web Vault.
2. Start a new Organization by selecting the {% icon fa-plus %} **Add Organization** button.
3. When prompted, upload the Organization license file and select **Submit**.

14
_articles/hosting/updating-on-premise.md
View File

@@ -36,5 +36,17 @@ Update your Bitwarden instance using the same Bash (Linux or macOS) or Powershel
Your Bitwarden installation should now be fully up to date and running.
{% callout success %}
We recommend creating a cronjob or scheduled task to run these update commands weekly, or even nightly. This will automatically keep your instance up to date.
We recommend creating a cronjob or scheduled task to run these update commands weekly, or even nightly, to keep your instance up to date. For example, the following cron job would check for an update every Sunday at 2:00 and turn off email output for the job:
```
0 2 * * 0 /opt/bitwarden/bwdata/scripts/updatebw.sh >/dev/null 2>&1
```
In the above example, `updatebw.sh` is a script you must save manually that contains:
```
#!/bin/bash
./bitwarden.sh updateself
./bitwarden.sh update
```
{% endcallout %}