mirror of
https://github.com/bitwarden/help
synced 2025-12-06 00:03:30 +00:00
Promote to Master (#748)
* initial commit
* adding quotes for the array error
* Create Gemfile
* Create Gemfile.lock
* add .nvmrc and .node-version
* removed /article from URL
* update links to work with netlify
* more fixed links
* link fixes
* update bad links
* Update netlify.toml
toml test for redirects
* article redirect
* link fixes
* Update index.html
* Update netlify.toml
* Update _config.yml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* add article back into URL for launch
* Update netlify.toml
* Update netlify.toml
* add order to categories front matter
* Update netlify.toml
* update
* sidemenu update
* Revert "sidemenu update"
This reverts commit 5441c3d35c.
* update order prop
* Navbar updates per Gary and compiler warnings
* font/style tweaks
* Update sidebar.html
* Stage Release Documentation (#739)
* initial drafts
* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information
* edit
* edit
* Custom Field Context Menu & CAPTCHA item in release notes
* SSO relink event
* update rn
* small edits
* improve release notes titles
* fix side menu
* Edits courtest of mportune!
* update order
* link fixes
* link cleanup
* image updates and a link
* fix trailing slash
Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
63f78e8979
commit
906e2ca0dd
2
.bundle/config
Normal file
2
.bundle/config
Normal file
@@ -0,0 +1,2 @@
|
||||
---
|
||||
BUNDLE_PATH: "vendor/bundle"
|
||||
1
.gitignore
vendored
1
.gitignore
vendored
@@ -11,3 +11,4 @@ _site/
|
||||
.vscode/*
|
||||
!.vscode/settings.json
|
||||
.DS_Store
|
||||
*.icloud
|
||||
|
||||
1
.node-version
Normal file
1
.node-version
Normal file
@@ -0,0 +1 @@
|
||||
v14.17.6
|
||||
1
.ruby-version
Normal file
1
.ruby-version
Normal file
@@ -0,0 +1 @@
|
||||
ruby 2.6.3
|
||||
3
Gemfile
Normal file
3
Gemfile
Normal file
@@ -0,0 +1,3 @@
|
||||
source "https://rubygems.org"
|
||||
gem "jekyll"
|
||||
gem 'jekyll-redirect-from'
|
||||
70
Gemfile.lock
Normal file
70
Gemfile.lock
Normal file
@@ -0,0 +1,70 @@
|
||||
GEM
|
||||
remote: https://rubygems.org/
|
||||
specs:
|
||||
addressable (2.8.0)
|
||||
public_suffix (>= 2.0.2, < 5.0)
|
||||
colorator (1.1.0)
|
||||
concurrent-ruby (1.1.9)
|
||||
em-websocket (0.5.2)
|
||||
eventmachine (>= 0.12.9)
|
||||
http_parser.rb (~> 0.6.0)
|
||||
eventmachine (1.2.7)
|
||||
ffi (1.15.4)
|
||||
forwardable-extended (2.6.0)
|
||||
http_parser.rb (0.6.0)
|
||||
i18n (1.8.10)
|
||||
concurrent-ruby (~> 1.0)
|
||||
jekyll (4.2.0)
|
||||
addressable (~> 2.4)
|
||||
colorator (~> 1.0)
|
||||
em-websocket (~> 0.5)
|
||||
i18n (~> 1.0)
|
||||
jekyll-sass-converter (~> 2.0)
|
||||
jekyll-watch (~> 2.0)
|
||||
kramdown (~> 2.3)
|
||||
kramdown-parser-gfm (~> 1.0)
|
||||
liquid (~> 4.0)
|
||||
mercenary (~> 0.4.0)
|
||||
pathutil (~> 0.9)
|
||||
rouge (~> 3.0)
|
||||
safe_yaml (~> 1.0)
|
||||
terminal-table (~> 2.0)
|
||||
jekyll-redirect-from (0.16.0)
|
||||
jekyll (>= 3.3, < 5.0)
|
||||
jekyll-sass-converter (2.1.0)
|
||||
sassc (> 2.0.1, < 3.0)
|
||||
jekyll-watch (2.2.1)
|
||||
listen (~> 3.0)
|
||||
kramdown (2.3.1)
|
||||
rexml
|
||||
kramdown-parser-gfm (1.1.0)
|
||||
kramdown (~> 2.0)
|
||||
liquid (4.0.3)
|
||||
listen (3.7.0)
|
||||
rb-fsevent (~> 0.10, >= 0.10.3)
|
||||
rb-inotify (~> 0.9, >= 0.9.10)
|
||||
mercenary (0.4.0)
|
||||
pathutil (0.16.2)
|
||||
forwardable-extended (~> 2.6)
|
||||
public_suffix (4.0.6)
|
||||
rb-fsevent (0.11.0)
|
||||
rb-inotify (0.10.1)
|
||||
ffi (~> 1.0)
|
||||
rexml (3.2.5)
|
||||
rouge (3.26.0)
|
||||
safe_yaml (1.0.5)
|
||||
sassc (2.4.0)
|
||||
ffi (~> 1.9)
|
||||
terminal-table (2.0.0)
|
||||
unicode-display_width (~> 1.1, >= 1.1.1)
|
||||
unicode-display_width (1.8.0)
|
||||
|
||||
PLATFORMS
|
||||
universal-darwin-20
|
||||
|
||||
DEPENDENCIES
|
||||
jekyll
|
||||
jekyll-redirect-from
|
||||
|
||||
BUNDLED WITH
|
||||
2.2.12
|
||||
@@ -3,7 +3,7 @@
|
||||
|
||||
# Bitwarden Help Center
|
||||
|
||||
The Bitwarden help center project is written using Jekyll, which is deployed at ([https://bitwarden.com/help/](https://bitwarden.com/help/)).
|
||||
The Bitwarden help center project is written using Jekyll, which is deployed at ([https://bitwarden.com/help/]({{site.baseurl}}/)).
|
||||
|
||||
# Build/Run
|
||||
|
||||
|
||||
@@ -5,12 +5,12 @@ categories: [security]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [encryption key, account]
|
||||
order: 04
|
||||
order: "04"
|
||||
redirect_from:
|
||||
- /article/update-encryption-key/
|
||||
---
|
||||
|
||||
Each unique Bitwarden account has an encryption key derived from your Master Password, according to the methods defined in [Encryption]({% link _articles/security/what-encryption-is-used.md %}). This encryption key is used to encrypt all Vault data.
|
||||
Each unique Bitwarden account has an encryption key derived from your Master Password, according to the methods defined in [Encryption]({{site.baseurl}}/article/what-encryption-is-used/). This encryption key is used to encrypt all Vault data.
|
||||
|
||||
## Rotate your Encryption Key
|
||||
|
||||
@@ -31,7 +31,7 @@ When you rotate an encryption key, you **must immediately** log out of any logge
|
||||
|
||||
#### Re-create any Encrypted Exports
|
||||
|
||||
If you're using [Encrypted Exports]({% link _articles/importing/encrypted-export.md %}) to store long-term secure backups, you should immediately re-create the encrypted export of your Vault data using the new encryption key.
|
||||
If you're using [Encrypted Exports]({{site.baseurl}}/article/encrypted-export/) to store long-term secure backups, you should immediately re-create the encrypted export of your Vault data using the new encryption key.
|
||||
|
||||
Encrypted Exports use your encryption key to encrypt **and decrypt** your Vault data, meaning that a rotated encryption key will not be able to decrypt an export created with the "stale" (prior-to-rotation) key.
|
||||
|
||||
|
||||
@@ -6,10 +6,10 @@ featured: true
|
||||
popular: true
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
|
||||
Login prompts like the one pictured below, called "basic" or "native" authentication prompts, will be automatically auto-filled by the Bitwarden Browser Extension **if there is only 1 Login item with a** [**matching URI**]({{site.baseurl}}/article/uri-match-detection). You can also use the Browser Extension's {% icon fa-share-square %} **Launch** button to automatically open and log in to a basic auth-protected resource.
|
||||
Login prompts like the one pictured below, called "basic" or "native" authentication prompts, will be automatically auto-filled by the Bitwarden Browser Extension **if there is only 1 Login item with a** [**matching URI**]({{site.baseurl}}/article/uri-match-detection/). You can also use the Browser Extension's {% icon fa-share-square %} **Launch** button to automatically open and log in to a basic auth-protected resource.
|
||||
|
||||
Auto-filling on basic auth prompts will, by default, use the [Host]({{site.baseurl}}/article/uri-match-detection/#host) URI match detection option so that auto-filling is more restrictive. This can be changed by setting the [match detection option]({{site.baseurl}}/article/uri-match-detection/) for the relevant Vault item.
|
||||
|
||||
@@ -23,6 +23,6 @@ The below animation shows the authentication flow in Google Chrome for autofille
|
||||
|
||||
{% image autofill/saving-basic-auth.gif Basic Auth Autofill flow %}
|
||||
|
||||
{% callout note %}
|
||||
{% callout info %}
|
||||
Due to the way basic auth prompts are designed, auto-filling must be non-interactive. This means you cannot auto-fill on a basic auth prompt using the {% icon fa-folder %} **Tab** view, context-menu, or keyboard shortcuts.
|
||||
{% endcallout %}
|
||||
|
||||
@@ -5,12 +5,12 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [unlock, face id, touch id, hello, windows, mac, ios, android]
|
||||
order: 11
|
||||
order: "11"
|
||||
---
|
||||
|
||||
Bitwarden can be configured to accept biometrics as a method to unlock your Vault.
|
||||
|
||||
Biometrics can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
Biometrics can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({{site.baseurl}}/article/setup-two-step-login/) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
|
||||
{% callout success %}
|
||||
Biometric features are part of the built-in security in your device and/or operating system. Bitwarden leverages native APIs to perform this validation, and therefore **Bitwarden does not receive any biometrics information** from the device.
|
||||
@@ -115,7 +115,7 @@ To enable Unlock with Biometrics for your Browser Extension:
|
||||
1. In your Bitwarden Desktop app, navigate to Settings (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
2. Scroll down to the Options section, and check the **Enable Browser Integration** box.
|
||||
|
||||
{% callout info %}Optionally, check the **Require verification for browser integration** option to require [account fingerprint]({% link _articles/features/fingerprint-phrase.md %}) verification when you activate the integration.{% endcallout %}
|
||||
{% callout info %}Optionally, check the **Require verification for browser integration** option to require [account fingerprint]({{site.baseurl}}/article/fingerprint-phrase/) verification when you activate the integration.{% endcallout %}
|
||||
3. In your Browser, navigate to the Extensions manager (e.g. `chrome://extensions` or `brave://extensions`), open Bitwarden, and toggle the **Allow access to file URLs** option.
|
||||
|
||||
|
||||
@@ -142,14 +142,14 @@ Your Desktop app needs to be **Logged In** but does not need to be **Unlocked**
|
||||
|
||||
## Understanding Unlock vs. Log In
|
||||
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({% link _articles/security/vault-data.md %}) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({% link _articles/security/what-encryption-is-used.md %}).
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({{site.baseurl}}/article/vault-data/) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({{site.baseurl}}/article/what-encryption-is-used/).
|
||||
|
||||
**Logging in** to Bitwarden **decrypts** your Vault data to your device. In practice, that means two things:
|
||||
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({% link _articles/two-step-login/setup-two-step-login.md %}) would be required.
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({{site.baseurl}}/article/setup-two-step-login/) would be required.
|
||||
2. Logging in will always require you to be connected to the internet (or, if you're self-hosting, connected to the server), because you need access to the encrypted Vault in order to decrypt it.
|
||||
|
||||
**Unlocking** can only be done when you're already logged in. In other words, only when your Vault data is already stored (encrypted) on your device. Because your Vault is already downloaded and your decryption key stored in memory:
|
||||
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({% link _articles/account/unlock-with-pin.md %}) and [biometrics]({% link _articles/account/biometrics.md %}).
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({{site.baseurl}}/article/unlock-with-pin/) and [biometrics]({{site.baseurl}}/article/biometrics/).
|
||||
2. You don't need to be connected to the internet (or, if you're self-hosting, connected to the server).
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [plans-and-pricing]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [account, delete]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
Deleting a Bitwarden account or Organization permanently deletes the account or Organization and **all data that is associated with it**. Bitwarden does not "soft delete" any data.
|
||||
@@ -42,7 +42,7 @@ If you're deleting the account because you lost your Master Password, you can no
|
||||
## Delete an Organization
|
||||
|
||||
{% callout info %}
|
||||
Only the **Owner** of an Organization has the authority to delete the Organization. For more information, see [User Types and Access Controls]({% link _articles/organizations/user-types-access-control.md %}).
|
||||
Only the **Owner** of an Organization has the authority to delete the Organization. For more information, see [User Types and Access Controls]({{site.baseurl}}/article/user-types-access-control/).
|
||||
{% endcallout %}
|
||||
|
||||
1. In the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}, open your Organization.
|
||||
|
||||
@@ -5,17 +5,17 @@ categories: [import-export]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [export, accounts, csv]
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
|
||||
You can export your personal Vault data from any client application, or export an Organization Vault from the Web Vault or CLI. Exports can be downloaded as plaintext `.json` or `.csv` files, or as a `.json` [encrypted export]({% link _articles/importing/encrypted-export.md %}).
|
||||
You can export your personal Vault data from any client application, or export an Organization Vault from the Web Vault or CLI. Exports can be downloaded as plaintext `.json` or `.csv` files, or as a `.json` [encrypted export]({{site.baseurl}}/article/encrypted-export/).
|
||||
|
||||
We recommend using `.json` for a more complete export, as `.csv` files won't currently export Cards or Identities. For complete information on the format of Bitwarden `.csv` and `.json` files, see [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
We recommend using `.json` for a more complete export, as `.csv` files won't currently export Cards or Identities. For complete information on the format of Bitwarden `.csv` and `.json` files, see [Condition a Bitwarden .csv or .json]({{site.baseurl}}/article/condition-bitwarden-import/).
|
||||
|
||||
Vault Exports **will not include** [file attachments]({% link _articles/features/attachments.md %}) or Items in the Trash.
|
||||
Vault Exports **will not include** [file attachments]({{site.baseurl}}/article/attachments/) or Items in the Trash.
|
||||
|
||||
{% callout warning %}
|
||||
Unless you're using an [Encrypted Export]({% link _articles/importing/encrypted-export.md %}), do not store or send the exported file over insecure channels, like email, and delete the file immediately after use.
|
||||
Unless you're using an [Encrypted Export]({{site.baseurl}}/article/encrypted-export/), do not store or send the exported file over insecure channels, like email, and delete the file immediately after use.
|
||||
{% endcallout %}
|
||||
|
||||
## Export a Personal Vault
|
||||
@@ -120,7 +120,7 @@ To export your personal Vault from the CLI, use the `export` command. By default
|
||||
bw export my-master-password --output /users/me/documents/ --format json
|
||||
```
|
||||
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more detail, see our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
@@ -129,7 +129,7 @@ For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli
|
||||
|
||||
## Export an Organization Vault
|
||||
|
||||
Organization [Admins and Owners]({% link _articles/organizations/user-types-access-control.md %}) can export their Organization Vault (i.e. all items owned by the Organization) from the Web Vault or CLI:
|
||||
Organization [Admins and Owners]({{site.baseurl}}/article/user-types-access-control/) can export their Organization Vault (i.e. all items owned by the Organization) from the Web Vault or CLI:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
@@ -174,7 +174,7 @@ bw export my-master-password --organizationid 7063feab-4b10-472e-b64c-785e2b870b
|
||||
If you don't know your `organizationid` value off-hand, you can access it at the command-line using `bw list organizations`.
|
||||
{% endcallout %}
|
||||
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more detail, see our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ org_cli_info | markdownify}}
|
||||
|
||||
@@ -5,10 +5,10 @@ categories: [account-management]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [master password, account]
|
||||
order: 02
|
||||
order: "02"
|
||||
---
|
||||
|
||||
As described in the [Your Master Password]({% link _articles/account/master-password.md %}) article, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password.
|
||||
As described in the [Your Master Password]({{site.baseurl}}/article/master-password/) article, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password.
|
||||
|
||||
If you've already lost your Master Password, there is unfortunately no way for anyone to recover the account or the data stored in your Personal Vault unless you're enrolled in [Organization Master Password Reset]({{site.baseurl}}/article/admin-reset/). You will need to delete your account and start a new one.
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ tags: [browser, safari]
|
||||
Bitwarden's Safari Web Extension is a port of the prior *App Extension* designed for use with [Safari 14](https://developer.apple.com/documentation/safariservices/safari_web_extensions/converting_a_safari_app_extension_to_a_safari_web_extension?language=objc){:target="\_blank"}. The Safari Web Extension is packaged with the Bitwarden Desktop App available on the App Store.
|
||||
|
||||
{% callout info %}
|
||||
Due to changes by Apple, Safari limits Web Extension use to **only those obtained through Mac App Store downloads**. As of the [2021-03-11 Release]({% link _articles/getting-started/releasenotes.md %}), users will not be able to use a Bitwarden Safari Extension obtained through a `.dmg` installation from [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} or any other non-App Store source.
|
||||
Due to changes by Apple, Safari limits Web Extension use to **only those obtained through Mac App Store downloads**. As of the [2021-03-11 Release]({{site.baseurl}}/article/releasenotes/), users will not be able to use a Bitwarden Safari Extension obtained through a `.dmg` installation from [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} or any other non-App Store source.
|
||||
|
||||
**If you're using a Safari version prior to 14**, you can continue using a `.dmg` installation, which can be downloaded from [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} by clicking **more desktop installation options >**. Keeping the `.dmg` outside of the Applications folder should allow you to simultaneously use both an older Safari Extension and the latest Desktop App.
|
||||
{% endcallout %}
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [keyboard, shortcut, mouseless]
|
||||
order: 15
|
||||
order: "15"
|
||||
---
|
||||
|
||||
## Browser extension shortcuts
|
||||
@@ -22,7 +22,7 @@ order: 15
|
||||
- Ctrl/CMD `+` Shift `+` 9 `→` Generate a password and copy it to the clipboard
|
||||
- Ctrl/CMD `+` Shift `+` N `→` Lock extension
|
||||
|
||||
{% callout success %}If a login uses the [Bitwarden Authenticator]({% link _articles/features/authenticator-keys.md %}) for TOTPs, using the `Cmd/Ctrl + Shift + L` will automatically copy your TOTP to your clipboard after auto-filling. All you have to do is `Cmd/Ctrl + V` to paste!
|
||||
{% callout success %}If a login uses the [Bitwarden Authenticator]({{site.baseurl}}/article/authenticator-keys/) for TOTPs, using the `Cmd/Ctrl + Shift + L` will automatically copy your TOTP to your clipboard after auto-filling. All you have to do is `Cmd/Ctrl + V` to paste!
|
||||
{% endcallout %}
|
||||
|
||||
## Desktop application shortcuts
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [account, items, import, delete, trash, clone]
|
||||
order: 03
|
||||
order: "03"
|
||||
---
|
||||
|
||||
Effectively managing the items in your Vault is key to making sure that you secure and have seamless access to your information, and can safely share information with friends, family, teams, and colleagues. There are 4 types of items you can store in your Vault; Logins, Cards, Identities, and Secure Notes:
|
||||
@@ -30,7 +30,7 @@ Effectively managing the items in your Vault is key to making sure that you secu
|
||||
{% capture logins %}
|
||||
### Logins
|
||||
|
||||
Login items are most often used to store username and password combinations, and support [TOTP seeds]({{site.baseurl}}/article/authenticator-keys/) for Premium users. Whatever plan you're on, we recommend giving every Login a [URI for easy auto-fill]({{site.baseurl}}/article/uri-match-detection):
|
||||
Login items are most often used to store username and password combinations, and support [TOTP seeds]({{site.baseurl}}/article/authenticator-keys/) for Premium users. Whatever plan you're on, we recommend giving every Login a [URI for easy auto-fill]({{site.baseurl}}/article/uri-match-detection/):
|
||||
|
||||
{% image manage-items/login-item.png Login Vault Item %}
|
||||
|
||||
@@ -73,7 +73,7 @@ Secure Notes can be used to store encrypted freeform text for anything you want
|
||||
</div>
|
||||
|
||||
{% callout success %}
|
||||
You can import items into your Vault from a variety of password management solutions. For more information, see [Import Data to your Vault]({% link _articles/importing/import-data.md %}).
|
||||
You can import items into your Vault from a variety of password management solutions. For more information, see [Import Data to your Vault]({{site.baseurl}}/article/import-data/).
|
||||
{% endcallout %}
|
||||
|
||||
## Manage Vault Items
|
||||
@@ -142,7 +142,7 @@ You can add, edit, and delete Vault items from any Bitwarden client application:
|
||||
{% capture cli_sync%}
|
||||
### CLI
|
||||
|
||||
For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more information, refer to our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_sync | markdownify }}
|
||||
@@ -151,7 +151,7 @@ For more information, refer to our [CLI documentation]({% link _articles/miscell
|
||||
|
||||
### Folders and Favorites
|
||||
|
||||
Items in your Vault can be organized into Folders, or marked as Favorites. For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
Items in your Vault can be organized into Folders, or marked as Favorites. For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Items in the Trash
|
||||
|
||||
@@ -173,7 +173,7 @@ Master password re-prompt **is not** an encryption mechanism. This feature is an
|
||||
|
||||
## Move Items to an Organization
|
||||
|
||||
If you're a member of an [Organization]({{site.baseurl}}/article/about-organizations/), you can move Vault items to your Organization for sharing with other Organization members. Learn more about [Organizations]({{site.baseurl}}/article/about-organizations/), [Collections]({{site.baseurl}}/article/about-collections), and [Sharing]({{site.baseurl}}/article/sharing/).
|
||||
If you're a member of an [Organization]({{site.baseurl}}/article/about-organizations/), you can move Vault items to your Organization for sharing with other Organization members. Learn more about [Organizations]({{site.baseurl}}/article/about-organizations/), [Collections]({{site.baseurl}}/article/about-collections/), and [Sharing]({{site.baseurl}}/article/sharing/).
|
||||
|
||||
## Clone Vault Items
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [master password, account]
|
||||
order: 01
|
||||
order: "01"
|
||||
redirect_from:
|
||||
- /article/change-your-master-password/
|
||||
---
|
||||
@@ -16,7 +16,7 @@ Your Master Password is the primary method for accessing your Vault. It's critic
|
||||
|
||||
- **Memorable**: Bitwarden is a zero knowledge solution. This means that the team at Bitwarden, as well as Bitwarden systems themselves, have no knowledge of, way to retrieve, or way to reset your Master Password. **Don't forget your Master Password!** Bitwarden won't be able to reset it or recover your Vault data if you do.
|
||||
|
||||
For our technically-inclined users, see the article on [Encryption]({% link _articles/security/what-encryption-is-used.md %}) to find out how we accomplish zero knowledge.
|
||||
For our technically-inclined users, see the article on [Encryption]({{site.baseurl}}/article/what-encryption-is-used/) to find out how we accomplish Zero Trust.
|
||||
- **Strong**: The longer, more complex, and less common your Master Password is, the safer your Vault data will be. Using something like `password` for your Master Password could let a capable attacker crack your Vault in **less than a second**!
|
||||
|
||||
Use Bitwarden's free [**Password Strength Testing Tool**](https://bitwarden.com/password-strength){:target="\_blank"} to test the strength of some Master Passwords you'd consider using.
|
||||
@@ -27,7 +27,7 @@ Your Master Password is the primary method for accessing your Vault. It's critic
|
||||
If you're worried about forgetting your Master Password, the team at Bitwarden has a few recommendations for you:
|
||||
|
||||
1. **Setup a Master Password Hint**. Once setup, a Master Password Hint can be requested on the Login Screen. The hint will be emailed to you, not displayed on the web page, so as long as your inbox isn't compromised you won't have to worry about prying eyes (that said, we don't recommend using a hint that would give away your Master Password to anyone other than yourself).
|
||||
2. **Designate a [Trusted Emergency Contact]({% link _articles/security/emergency-access.md %})**. If you have a Premium subscription, you can proactively configure your Vault to grant access in the case of emergency to another Bitwarden user.
|
||||
2. **Designate a [Trusted Emergency Contact]({{site.baseurl}}/article/emergency-access/)**. If you have a Premium subscription, you can proactively configure your Vault to grant access in the case of emergency to another Bitwarden user.
|
||||
|
||||
{% endcallout %}
|
||||
|
||||
@@ -36,7 +36,7 @@ If you're worried about forgetting your Master Password, the team at Bitwarden h
|
||||
Provided you **know your current Master Password**, change your Master Password at any time from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
|
||||
{% callout success %}
|
||||
If you don't know your Master Password, see [I Forgot my Master Password]({% link _articles/account/forgot-master-password.md %}).
|
||||
If you don't know your Master Password, see [I Forgot my Master Password]({{site.baseurl}}/article/forgot-master-password/).
|
||||
{% endcallout %}
|
||||
|
||||
1. In your Web Vault, Select the **Settings** tab from the top navigation.
|
||||
@@ -44,7 +44,7 @@ If you don't know your Master Password, see [I Forgot my Master Password]({% lin
|
||||
3. Enter your **Current Master Password**.
|
||||
4. Enter and Confirm your **New Master Password**.
|
||||
|
||||
{% callout warning %}Don't check the **rotate account's encryption key** box unless you fully understand the ramifications and required follow-up procedures. Learn more [here]({% link _articles/account/account-encryption-key.md %}).{% endcallout %}
|
||||
{% callout warning %}Don't check the **rotate account's encryption key** box unless you fully understand the ramifications and required follow-up procedures. Learn more [here]({{site.baseurl}}/article/account-encryption-key/).{% endcallout %}
|
||||
5. Select the **Change Master Password** button.
|
||||
|
||||
Changing your Master Password will log you out of your current Web Vault session, requiring you to log back in with your new Master Password.
|
||||
|
||||
@@ -5,12 +5,12 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [unlock, pin]
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
Bitwarden can be configured to accept a Personal Identification Number (PIN) as a method to unlock your Vault.
|
||||
|
||||
PINs can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
PINs can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({{site.baseurl}}/article/setup-two-step-login/) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
|
||||
## Enable Unlock with PIN
|
||||
|
||||
@@ -97,14 +97,14 @@ When using the **Lock with master password on restart** PIN option, the Bitwarde
|
||||
|
||||
## Understanding Unlock vs. Log In
|
||||
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({% link _articles/security/vault-data.md %}) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({% link _articles/security/what-encryption-is-used.md %}).
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({{site.baseurl}}/article/vault-data/) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({{site.baseurl}}/article/what-encryption-is-used/).
|
||||
|
||||
**Logging in** to Bitwarden **decrypts** your Vault data to your device. In practice, that means two things:
|
||||
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({% link _articles/two-step-login/setup-two-step-login.md %}) would be required.
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({{site.baseurl}}/article/setup-two-step-login/) would be required.
|
||||
2. Logging in will always require you to be connected to the internet (or, if you're self-hosting, connected to the server), because you need access to the encrypted Vault in order to decrypt it.
|
||||
|
||||
**Unlocking** can only be done when you're already logged in. In other words, only when your Vault data is already stored (encrypted) on your device. Because your Vault is already downloaded and your decryption key stored in memory:
|
||||
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({% link _articles/account/unlock-with-pin.md %}) and [biometrics]({% link _articles/account/biometrics.md %}).
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({{site.baseurl}}/article/unlock-with-pin/) and [biometrics]({{site.baseurl}}/article/biometrics/).
|
||||
2. You don't need to be connected to the internet (or, if you're self-hosting, connected to the server).
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [account, vault, timeout, 2FA, two-step]
|
||||
order: 14
|
||||
order: "14"
|
||||
---
|
||||
|
||||
Vault Timeout behavior will determine how your Vault will behave after a customizable period of inactivity. Timeout is configured individually from and for each Bitwarden client application that you use (Mobile, Web, Desktop, Browser Extension, etc.).
|
||||
@@ -32,7 +32,7 @@ Configuring this option will dictate what Bitwarden will do once the Vault Timeo
|
||||
|
||||
- **Lock** (*default*).
|
||||
|
||||
Locking your Vault will maintain Vault data on the device. You will only be prompted to enter your Master Password to decrypt your Vault, however no [Two-step Login]({% link _articles/two-step-login/setup-two-step-login.md %}) method will be required to unlock your Vault.
|
||||
Locking your Vault will maintain Vault data on the device. You will only be prompted to enter your Master Password to decrypt your Vault, however no [Two-step Login]({{site.baseurl}}/article/setup-two-step-login/) method will be required to unlock your Vault.
|
||||
|
||||
Bitwarden client applications don't need to be online to unlock.
|
||||
|
||||
@@ -42,6 +42,6 @@ Due to the storage and reference of your decryption keys within the Web Vault, u
|
||||
|
||||
- **Log Out**.
|
||||
|
||||
Logging Out of your Vault completely removes all Vault data from your device, and will therefore require you to re-authenticate to access your Vault. You will be required to enter your Email Address, Master Password, and any enabled [Two-step Login]({% link _articles/two-step-login/setup-two-step-login.md %}) method in order to access your Vault.
|
||||
Logging Out of your Vault completely removes all Vault data from your device, and will therefore require you to re-authenticate to access your Vault. You will be required to enter your Email Address, Master Password, and any enabled [Two-step Login]({{site.baseurl}}/article/setup-two-step-login/) method in order to access your Vault.
|
||||
|
||||
Bitwarden client applications must be online to log in.
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 09
|
||||
order: "09"
|
||||
---
|
||||
|
||||
This article will help you get started using Directory Connector to sync users and groups from your Azure Active Directory to your Bitwarden Organization.
|
||||
@@ -67,7 +67,7 @@ Complete the following steps to obtain the tenant hostname to be used by Directo
|
||||
|
||||
Complete the following steps to configure Directory Connector to use your Azure Active Directory. If you haven't already, take the proper [Azure AD Setup](#azure-ad-setup) steps before proceeding:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. From the **Type** dropdown, select **Azure Active Directory**.
|
||||
|
||||
@@ -78,12 +78,12 @@ Complete the following steps to configure Directory Connector to use your Azure
|
||||
## Configure Sync Options
|
||||
|
||||
{% callout success %}
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to configure the settings used when syncing using Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. In the **Sync** section, configure the following options as desired:
|
||||
|
||||
@@ -166,7 +166,7 @@ If you get the error message `Resource <user id> does not exist or one of its qu
|
||||
|
||||
Once [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters) are configured and tested, you can begin syncing. Complete the following steps to start automatic syncing with Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Dashboard** tab.
|
||||
3. In the **Sync** section, select the **Start Sync** button.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
Directory Connector keeps a local cache while syncing changes to your Bitwarden Organization. This cache allows Directory Connector to **only send the deltas between the two directories** (before / after).
|
||||
@@ -14,6 +14,6 @@ If you encounter sync errors, or if a particular directory change is not being s
|
||||
|
||||
To clear the local cache:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **More** tab.
|
||||
3. In the **Other** section, select the **Clear Sync Cache** button.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 03
|
||||
order: "03"
|
||||
---
|
||||
|
||||
The Directory Connector CLI is suited toward work in environments where a desktop GUI is unavailable, or if you want to programmatically script directory sync operations using tools provided by the operating system (cron job, scheduled task, etc.). The Directory Connector CLI can be used cross-platform on Windows, macOS, and Linux distributions.
|
||||
@@ -33,11 +33,11 @@ To get started using the Bitwarden Directory Connector CLI:
|
||||
bwdc --help
|
||||
```
|
||||
4. Connect Directory Connector to your Directory using the `bwdc config <setting> <value>` command (see [command reference](#config)).
|
||||
5. Configure Sync Options by editing your `data.json` file (to learn more, see [Directory Connector File Storage]({% link _articles/directory-connector/directory-sync-shared.md %})). Use the `bwdc data-file` command to obtain the absolute path of your `data.json` file.
|
||||
5. Configure Sync Options by editing your `data.json` file (to learn more, see [Directory Connector File Storage]({{site.baseurl}}/article/directory-sync-shared/)). Use the `bwdc data-file` command to obtain the absolute path of your `data.json` file.
|
||||
|
||||
Available **Sync Options** depend on the directory type in use, so refer to one of the following articles for a list of options available to you:
|
||||
- [Sync with Active Directory or LDAP]({% link _articles/directory-connector/ldap-directory.md %})
|
||||
- [Sync with Azure Active Directory]({% link _articles/directory-connector/azure-active-directory.md %})
|
||||
- [Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)
|
||||
- [Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)
|
||||
- [Sync with G Suite (Google)]({% link _articles/directory-connector/gsuite-directory.md %})
|
||||
- [Sync with Okta]({% link _articles/directory-connector/okta-directory.md %})
|
||||
- [Sync with OneLogin]({% link _articles/directory-connector/onelogin-directory.md %})
|
||||
@@ -140,7 +140,7 @@ Options include:
|
||||
- `onelogin.secret <secret>`
|
||||
|
||||
{% callout success %}
|
||||
`ldap.password`, `azure.key`, `gsuite.key`, `okta.token`, and `onelogin.secret` can **only** be modified from the CLI using `bwdc config`, or from the [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
`ldap.password`, `azure.key`, `gsuite.key`, `okta.token`, and `onelogin.secret` can **only** be modified from the CLI using `bwdc config`, or from the [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
{% endcallout %}
|
||||
|
||||
### data-file
|
||||
@@ -154,7 +154,7 @@ Configuration settings can be modified for the Directory Connector CLI by editin
|
||||
|
||||
### clear-cache
|
||||
|
||||
The `clear-cache` command allows you to clear cached data that the application stores while performing sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
The `clear-cache` command allows you to clear cached data that the application stores while performing sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
|
||||
```
|
||||
bwdc clear-cache
|
||||
|
||||
@@ -5,14 +5,14 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 02
|
||||
order: "02"
|
||||
---
|
||||
|
||||
The Directory Connector Desktop App is a standalone desktop application that can be used to sync users, groups, and group associations from a selection of directory services.
|
||||
|
||||
{% image directory-connector/app.png Directory Connector Desktop App %}
|
||||
|
||||
Directory Connector is also available as a [CLI Tool]({{site.baseurl}}/article/directory-sync-cli). The Desktop App and CLI [share a database and configurations]({% link _articles/directory-connector/directory-sync-shared.md %}), so you may choose to use both, however simultaneous use is not recommended.
|
||||
Directory Connector is also available as a [CLI Tool]({{site.baseurl}}/article/directory-sync-cli/). The Desktop App and CLI [share a database and configurations]({{site.baseurl}}/article/directory-sync-shared/), so you may choose to use both, however simultaneous use is not recommended.
|
||||
|
||||
## Getting Started
|
||||
|
||||
@@ -33,8 +33,8 @@ To get started using the Directory Connector Desktop App:
|
||||
3. Log in to Directory Connector using your [Organization API Key]({{site.baseurl}}/article/public-api/#authentication). If you don't have the API Key, reach out to an [Organization Owner]({{site.baseurl}}/article/user-types-access-control/).
|
||||
4. On the {% icon fa-cogs %} **Settings** tab, connect to your directory and configure [sync options]({{site.baseurl}}/article/user-group-filters/). This procedure will vary based on the directory in use, so refer to one of the following articles for instruction:
|
||||
|
||||
- [Sync with Active Directory or LDAP]({% link _articles/directory-connector/ldap-directory.md %})
|
||||
- [Sync with Azure Active Directory]({% link _articles/directory-connector/azure-active-directory.md %})
|
||||
- [Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)
|
||||
- [Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)
|
||||
- [Sync with G Suite (Google)]({% link _articles/directory-connector/gsuite-directory.md %})
|
||||
- [Sync with Okta]({% link _articles/directory-connector/okta-directory.md %})
|
||||
- [Sync with OneLogin]({% link _articles/directory-connector/onelogin-directory.md %})
|
||||
|
||||
@@ -5,10 +5,10 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 04
|
||||
order: "04"
|
||||
---
|
||||
|
||||
The Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}) and [CLI]({% link _articles/directory-connector/directory-sync-cli.md %}) share the same database and configuration settings. You may install and use both applications, however **it is not recommended to use them simultaneously**.
|
||||
The Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/) and [CLI]({{site.baseurl}}/article/directory-sync-cli/) share the same database and configuration settings. You may install and use both applications, however **it is not recommended to use them simultaneously**.
|
||||
|
||||
{% callout success %}
|
||||
Though not required, it may be helpful to use the Desktop Application first to setup and configure all of your settings before using the Directory Connector CLI.
|
||||
@@ -20,9 +20,9 @@ The Directory Connector configuration file (`data.json`) contains objects you ma
|
||||
- Set the connection to your Directory
|
||||
- Configure Sync Options
|
||||
|
||||
It is not possible to setup the *entirety* of Directory Connector from `data.json`. Authentication values, like keys or secrets, must be set from either the [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}) or [CLI]({% link _articles/directory-connector/directory-sync-cli.md %}).
|
||||
It is not possible to setup the *entirety* of Directory Connector from `data.json`. Authentication values, like keys or secrets, must be set from either the [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/) or [CLI]({{site.baseurl}}/article/directory-sync-cli/).
|
||||
|
||||
[{% icon fa-download %} Download a sample configuration file]({{site.baseurl}}/files/data.json)
|
||||
[{% icon fa-download %} Download a sample configuration file]({{site.baseurl}}/files/data.json/)
|
||||
|
||||
{% callout warning %}
|
||||
Avoid opening or modifying `data.json` while the Directory Connector Desktop Application or CLI executable is running.
|
||||
@@ -38,13 +38,13 @@ The location of `data.json` depends on which platform is in use:
|
||||
- Linux: `~/.config/Bitwarden Directory Connector`
|
||||
|
||||
{% callout success %}
|
||||
Using the Directory Connector [CLI]({% link _articles/directory-connector/directory-sync-cli.md %}), run the `data-file` command to discover the absolute path to the `data.json`.
|
||||
Using the Directory Connector [CLI]({{site.baseurl}}/article/directory-sync-cli/), run the `data-file` command to discover the absolute path to the `data.json`.
|
||||
{% endcallout %}
|
||||
|
||||
|
||||
## Secret Storage
|
||||
|
||||
By default, the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}) and [CLI]({% link _articles/directory-connector/directory-sync-cli.md %}) both use a secure method for persisting sensitive data (such as your directory account password, API keys, etc).
|
||||
By default, the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/) and [CLI]({{site.baseurl}}/article/directory-sync-cli/) both use a secure method for persisting sensitive data (such as your directory account password, API keys, etc).
|
||||
|
||||
On Linux systems this requires [GNOME Keyring](https://wiki.archlinux.org/index.php/GNOME/Keyring){:target="\_blank"} and [X11](https://en.wikipedia.org/wiki/X_Window_System){:target="\_blank"}, which are usually reserved for desktop environments. If you are using a headless Linux environment you may encounter errors such as:
|
||||
```
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [directory connector, directory sync, teams, enterprise]
|
||||
order: 01
|
||||
order: "01"
|
||||
---
|
||||
|
||||
## What is Directory Connector?
|
||||
@@ -24,8 +24,8 @@ A Directory Connector sync operation can be run on-demand or automatically on a
|
||||
|
||||
Directory Connector supports sync from the following sources:
|
||||
|
||||
- [Active Directory]({% link _articles/directory-connector/ldap-directory.md%})
|
||||
- [Any LDAP-based directory]({% link _articles/directory-connector/ldap-directory.md %})
|
||||
- [Active Directory]({{site.baseurl}}/article/ldap-directory/)
|
||||
- [Any LDAP-based directory]({{site.baseurl}}/article/ldap-directory/)
|
||||
- [Azure Active Directory]({% link _articles/directory-connector/azure-active-directory.md %})
|
||||
- [G Suite]({% link _articles/directory-connector/gsuite-directory.md %})
|
||||
- [Okta]({% link _articles/directory-connector/okta-directory.md %})
|
||||
@@ -33,7 +33,7 @@ Directory Connector supports sync from the following sources:
|
||||
|
||||
## Directory Connector Applications
|
||||
|
||||
Directory Connector is available as a cross-platform [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}) and as a [Command Line Interface (CLI)]({% link _articles/directory-connector/directory-sync-cli.md %}). The Desktop App and CLI [share a database and configurations]({% link _articles/directory-connector/directory-sync-shared.md %}), so you may choose to use both, however simultaneous use is not recommended.
|
||||
Directory Connector is available as a cross-platform [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/) and as a [Command Line Interface (CLI)]({{site.baseurl}}/article/directory-sync-cli/). The Desktop App and CLI [share a database and configurations]({{site.baseurl}}/article/directory-sync-shared/), so you may choose to use both, however simultaneous use is not recommended.
|
||||
|
||||
{% image directory-connector/app.png Directory Connector Desktop App %}
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
This article will help you get started using Directory Connector to sync users and groups from your Google Workspace (formerly "G Suite") Directory to your Bitwarden Organization.
|
||||
@@ -78,7 +78,7 @@ Complete the following steps to authorize the client to read your directory:
|
||||
|
||||
Complete the following steps to configure Directory Connector to use your Google directory:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. From the **Type** dropdown, select **G Suite (Google)**.
|
||||
|
||||
@@ -92,12 +92,12 @@ Complete the following steps to configure Directory Connector to use your Google
|
||||
## Configure Sync Options
|
||||
|
||||
{% callout success %}
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to configure the setting used when syncing using Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. In the **Sync** section, confiture the following options as desired:
|
||||
|
||||
@@ -169,7 +169,7 @@ To test whether Directory Connector will successfully connect to your directory
|
||||
|
||||
Once [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters) are configured and tested, you can begin syncing. Complete the following steps to start automatic syncing with Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Dashboard** tab.
|
||||
3. In the **Sync** section, select the **Start sync** button.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [active directory, ldap, ad]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
This article will help you get started using Directory Connector to sync users and groups from your LDAP or Active Directory service to your Bitwarden Organization. Bitwarden provides built-in connectors for the most popular LDAP directory servers, including:
|
||||
@@ -24,7 +24,7 @@ This article will help you get started using Directory Connector to sync users a
|
||||
|
||||
Complete the following steps to configure Directory Connector to use your LDAP or Active Directory:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. From the **Type** dropdown, select **Active Directory / LDAP**.
|
||||
|
||||
@@ -47,7 +47,7 @@ Complete the following steps to configure Directory Connector to use your LDAP o
|
||||
## Configure Sync Options
|
||||
|
||||
{% callout success %}
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to configure the settings used when syncing using Directory Connector:
|
||||
@@ -56,7 +56,7 @@ Complete the following steps to configure the settings used when syncing using D
|
||||
If you are using Active Directory, many of these settings are predetermined for you and are therefore are not shown.
|
||||
{% endcallout %}
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. In the **Sync** section, configure the following options as disired:
|
||||
|
||||
@@ -126,7 +126,7 @@ To test whether Directory Connector will successfully connect to your Directory
|
||||
|
||||
Once [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters) are configured and tested, you can begin syncing. Complete the following steps to start automatic syncing with Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Dashboard** tab.
|
||||
3. In the **Sync** section, select the **Start Sync** button.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 11
|
||||
order: "11"
|
||||
---
|
||||
|
||||
This article will help you get starting using Directory Connector to sync users and groups from your Okta directory to your Bitwarden Organization.
|
||||
@@ -25,7 +25,7 @@ Directory Connector requires knowledge of an Okta-generated token to connect to
|
||||
|
||||
Complete the following steps to configure Directory Connector to use your Okta Directory:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. From the **Type** dropdown, select **Okta**.
|
||||
|
||||
@@ -37,12 +37,12 @@ Complete the following steps to configure Directory Connector to use your Okta D
|
||||
## Configure Sync Options
|
||||
|
||||
{% callout success %}
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to configure the settings used when syncing using Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. In the **Sync** section, configure the following options as desired:
|
||||
|
||||
@@ -125,7 +125,7 @@ To test whether Directory Connector will successfully connect to your directory
|
||||
|
||||
Once [Sync Options](#configured-sync-options) and [Filters](#specify-sync-filters) are configured as desired, you can begin syncing. Complete the following steps to start automatic sync with Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Dashboard** tab.
|
||||
3. In the **Sync** section, select the **Start Sync** button.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 12
|
||||
order: "12"
|
||||
---
|
||||
|
||||
This article will help you get started using Directory Connector to sync users and groups from your OneLogin directory to your Bitwarden Organization.
|
||||
@@ -24,7 +24,7 @@ Directory Connector requires knowledge of OneLogin-generated API Credentials to
|
||||
|
||||
Complete the following steps to configure Directory Connector to use your OneLogin directory:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. From the **Type** dropdown, select **OneLogin**.
|
||||
|
||||
@@ -36,12 +36,12 @@ Complete the following steps to configure Directory Connector to use your OneLog
|
||||
## Configure Sync Options
|
||||
|
||||
{% callout success %}
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({% link _articles/directory-connector/clear-sync-cache.md %}).
|
||||
When you're finished configuring, navigate to the **More** tab and select the **Clear Sync Cache** button to prevent potential conflicts with prior sync operations. For more information, see [Clear Sync Cache]({{site.baseurl}}/article/clear-sync-cache/).
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to configure the settings used when syncing using Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Settings** tab.
|
||||
3. In the **Sync** section, configure the following options as desired:
|
||||
|
||||
@@ -97,7 +97,7 @@ To test whether Directory Connector will successfully connect to your directory
|
||||
|
||||
Once [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters) are configured as desired, you can begin syncing. Complete the following steps to start automatic sync with Directory Connector:
|
||||
|
||||
1. Open the Directory Connector [Desktop Application]({% link _articles/directory-connector/directory-sync-desktop.md %}).
|
||||
1. Open the Directory Connector [Desktop Application]({{site.baseurl}}/article/directory-sync-desktop/).
|
||||
2. Navigate to the **Dashboard** tab.
|
||||
3. In the **Sync** section, select the **Start Sync** button.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [directory-connector]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [directory connector, directory sync, schedule, cronjob]
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
|
||||
For Organizations using the Directory Connector CLI, automatic syncs can be scheduled on defined intervals as an alternative to using the Desktop Applications **Interval** setting. This is particularly useful in headless environments, on in circumstances where a Desktop Application cannot be left running in the background.
|
||||
|
||||
@@ -6,21 +6,21 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
When configuring the Directory Connector application, you can use a variety of Sync Options and Filters to customize your sync operation and limit the users and/or groups that are processed to your Bitwarden Organization.
|
||||
|
||||
Available Sync Options and Filter syntaxes are different for each directory server type. Refer to the **Configure Sync Options** and **Specify Sync Filters** sections of one of the following articles for help:
|
||||
|
||||
- [Sync with Active Directory or LDAP]({% link _articles/directory-connector/ldap-directory.md %})
|
||||
- [Sync with Azure Active Directory]({% link _articles/directory-connector/azure-active-directory.md %})
|
||||
- [Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)[Sync with Active Directory or LDAP]({{site.baseurl}}/article/ldap-directory/)
|
||||
- [Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)[Sync with Azure Active Directory]({{site.baseurl}}/article/azure-active-directory/)
|
||||
- [Sync with G Suite (Google)]({% link _articles/directory-connector/gsuite-directory.md %})
|
||||
- [Sync with Okta]({% link _articles/directory-connector/okta-directory.md %})
|
||||
- [Sync with OneLogin]({% link _articles/directory-connector/onelogin-directory.md %})
|
||||
|
||||
{% callout success%}
|
||||
If you're using the Directory Connector CLI, see [Directory Connector File Storage]({% link _articles/directory-connector/directory-sync-shared.md %}) for help editing your `data.json` configuration file.
|
||||
If you're using the Directory Connector CLI, see [Directory Connector File Storage]({{site.baseurl}}/article/directory-sync-shared/) for help editing your `data.json` configuration file.
|
||||
{% endcallout %}
|
||||
|
||||
## Large Syncs
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: true
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
### Q: Can I auto-fill on a split login-workflow?
|
||||
@@ -38,4 +38,4 @@ order: 10
|
||||
2. Log out of your Bitwarden mobile app.
|
||||
3. Check that your device settings are [setup to use Bitwarden for autofill]({{site.baseurl}}/article/auto-fill-ios/#keyboard-auto-fill).
|
||||
4. Log back in to your Bitwarden mobile app.
|
||||
5. Re-enable [PIN Code]({{site.baseurl}}/article/unlock-with-pin/) verification if you want to use it as a backup for [biometrics]({{site.baseurl}}/article/unlock-with-biometrics/).
|
||||
5. Re-enable [PIN Code]({{site.baseurl}}/article/unlock-with-pin/) verification if you want to use it as a backup for [biometrics]({{site.baseurl}}/article/biometrics/).
|
||||
|
||||
@@ -6,12 +6,12 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 09
|
||||
order: "09"
|
||||
---
|
||||
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Plans and Pricing**.
|
||||
|
||||
For help selecting the right Bitwarden plan for you, refer to [What Plan is Right for Me?]({% link _articles/plans-and-pricing/what-plan-is-right-for-me.md %}) and [About Bitwarden Plans]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}).
|
||||
For help selecting the right Bitwarden plan for you, refer to [What Plan is Right for Me?]({{site.baseurl}}/article/what-plan-is-right-for-me/) and [About Bitwarden Plans]({{site.baseurl}}/article/about-bitwarden-plans/).
|
||||
|
||||
## Account Management
|
||||
|
||||
@@ -24,15 +24,15 @@ For help selecting the right Bitwarden plan for you, refer to [What Plan is Righ
|
||||
|
||||
### Q: How do I view my billing information?
|
||||
|
||||
**A:** Viewing Billing information is different depending on whether you're viewing it for an Individual or Organization subscription. Use [Update Your Billing Information](https://bitwarden.com/help/article/update-billing-info/) to guide you through both processes.
|
||||
**A:** Viewing Billing information is different depending on whether you're viewing it for an Individual or Organization subscription. Use [Update Your Billing Information]({{site.baseurl}}/article/update-billing-info/) to guide you through both processes.
|
||||
|
||||
### Q: How do I delete my account?
|
||||
|
||||
**A:** We're sad to see you go! Use [Delete Your Account](https://help.bitwarden.com/article/delete-your-account/) to guide you through this process.
|
||||
**A:** We're sad to see you go! Use [Delete Your Account](https://help.bitwarden.com/delete-your-account/) to guide you through this process.
|
||||
|
||||
### Q: How do I upgrade from an Individual subscription to an Organization?
|
||||
|
||||
**A:** Use [Upgrade from Individual to Organization](https://bitwarden.com/help/article/upgrade-from-individual-to-org/) to guide you through this process.
|
||||
**A:** Use [Upgrade from Individual to Organization]({{site.baseurl}}/article/upgrade-from-individual-to-org/) to guide you through this process.
|
||||
|
||||
### Q: How do I add or remove a user seat from my Organization?
|
||||
|
||||
@@ -46,7 +46,7 @@ You can add or remove seats from your Organization at any time. The cost will be
|
||||
|
||||
**A:** In order to pay for a self-hosted instance of Bitwarden, you'll need to create an account in the Bitwarden cloud via the [Web Vault](https://vault.bitwarden.com). From there, you can download the license file to apply to your self-hosted instance. Your license file will flag your access to Premium features, so make sure that you download a new license file if you were previously on a free plan.
|
||||
|
||||
For more information, see [Hosting](https://bitwarden.com/help/hosting).
|
||||
For more information, see [Hosting]({{site.baseurl}}/article/hosting).
|
||||
|
||||
### Q: If I have a Families Organization, do I need Premium?
|
||||
|
||||
@@ -66,7 +66,7 @@ Legacy Families plans do not automatically provide premium features, so users wo
|
||||
|
||||
### Q: Can I pay with Bitcoin?
|
||||
|
||||
**A:** Yes! Refer to [Update Your Billing Information](https://bitwarden.com/help/article/update-billing-info/) for more information.
|
||||
**A:** Yes! Refer to [Update Your Billing Information]({{site.baseurl}}/article/update-billing-info/) for more information.
|
||||
|
||||
[Contact Us](https://bitwarden.com/contact/) once you have added the credit for the subscription amount. We will generate and send you an invoice and activate the new account. You will also receive an invoice from our payment processor (BitPay) at the time the Bitcoin is sent.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: true
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 13
|
||||
order: "13"
|
||||
---
|
||||
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Self-hosting**.
|
||||
@@ -25,7 +25,7 @@ You can read more about Docker and container technologies at [Docker's Website](
|
||||
|
||||
### Q: How do I backup and restore my self-hosted instance?
|
||||
|
||||
**A:** Bitwarden takes automated nightly backups of the `bitwarden-mssql` database container in order to protect your stored credentials. For help with manual backups, or help restoring a backup, see [Backup your Hosted Data]({% link _articles/hosting/backup-on-premise.md %}).
|
||||
**A:** Bitwarden takes automated nightly backups of the `bitwarden-mssql` database container in order to protect your stored credentials. For help with manual backups, or help restoring a backup, see [Backup your Hosted Data]({{site.baseurl}}/article/backup-on-premise/).
|
||||
|
||||
### Q: What are my installation id and installation key used for?
|
||||
|
||||
@@ -45,13 +45,13 @@ Retrieve an installation id and key from [https://bitwarden.com/host](https://bi
|
||||
|
||||
Check that your server name or FQDN has been proliferated to all `globalSettings_baseServiceUri__*` variables in `./bwdata/env/global.override.env`, and that your certificate contains a Subject Alternative Name (SAN) with the new server FQDN
|
||||
|
||||
If you are using Let's Encrypt certificate, you'll need to [Manually Update Your Certificate](https://bitwarden.com/help/article/certificates/#manually-update-a-lets-encrypt-certificate){:target="\_blank"}.
|
||||
If you are using Let's Encrypt certificate, you'll need to [Manually Update Your Certificate]({{site.baseurl}}/article/certificates/#manually-update-a-lets-encrypt-certificate){:target="\_blank"}.
|
||||
|
||||
## SMTP Configuration
|
||||
|
||||
### Q: How do I set up an SMTP Mail Server?
|
||||
|
||||
**A:** Connect your self-hosted instance to an existing SMTP Mail Server by editing all `globalSettings__mail__smtp__*` values in `./bwdata/env/global.overide.env`. For more information, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %}).
|
||||
**A:** Connect your self-hosted instance to an existing SMTP Mail Server by editing all `globalSettings__mail__smtp__*` values in `./bwdata/env/global.overide.env`. For more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|
||||
|
||||
If you don't yet have an existing SMTP Mail Server from which you can relay emails, consider services like [Mailgun](https://www.mailgun.com/){:target="\_blank"} or [SparkPost](https://www.sparkpost.com){:target="\_blank"}, or use Gmail an SMTP Mail Server.
|
||||
|
||||
@@ -82,7 +82,7 @@ Check that the custom port values have been proliferated to `./bwdata/env/global
|
||||
|
||||
### Q: How do I add Bitwarden to system boot?
|
||||
|
||||
**A:** Before adding Bitwarden to system boot, complete [Docker Post-Installation](https://bitwarden.com/help/article/install-on-premise/#docker-post-installation-linux-only) to setup a dedicated `bitwarden` service account.
|
||||
**A:** Before adding Bitwarden to system boot, complete [Docker Post-Installation]({{site.baseurl}}/article/install-on-premise/#docker-post-installation-linux-only) to setup a dedicated `bitwarden` service account.
|
||||
|
||||
Then, complete the following steps:
|
||||
|
||||
|
||||
@@ -6,14 +6,14 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Import & Export**.
|
||||
|
||||
### Q: How do I import my data if I don’t see my service on the import options list?
|
||||
|
||||
**A:** If we don't have official support for the service you are using, manually condition a `.csv` or `.json` for import into Bitwarden. For more information about how to do this, see [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
**A:** If we don't have official support for the service you are using, manually condition a `.csv` or `.json` for import into Bitwarden. For more information about how to do this, see [Condition a Bitwarden .csv or .json]({{site.baseurl}}/article/condition-bitwarden-import/).
|
||||
|
||||
### Q: Can I import to Bitwarden from iCloud/Mac Keychain?
|
||||
|
||||
@@ -27,11 +27,11 @@ Here are some third-party programs available to export this data:
|
||||
**Disclaimer**: These 3rd party scripts/programs are unsupported by Bitwarden or Apple, and should be used at your own risk.
|
||||
{% endcallout %}
|
||||
|
||||
Once exported from iCloud, Mac Keychain, or Safari, see [Import Data to your Vault]({% link _articles/importing/import-data.md %}).
|
||||
Once exported from iCloud, Mac Keychain, or Safari, see [Import Data to your Vault]({{site.baseurl}}/article/import-data/).
|
||||
|
||||
### Q: How do I import items directly to Collections?
|
||||
|
||||
**A:** To import items directly to Collections, format your import as a Bitwarden `.csv` (for more information, see [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %})) and specify Collections to import each item to within the file.
|
||||
**A:** To import items directly to Collections, format your import as a Bitwarden `.csv` (for more information, see [Condition a Bitwarden .csv or .json]({{site.baseurl}}/article/condition-bitwarden-import/)) and specify Collections to import each item to within the file.
|
||||
|
||||
### Q: How do I import file attachments to Bitwarden?
|
||||
|
||||
@@ -53,42 +53,42 @@ Please note that storage of File Attachments is available only for Premium users
|
||||
**A:** The following formats are supported out-of-the-box:
|
||||
|
||||
{% callout info %}
|
||||
If your format is not listed below, manually [condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
If your format is not listed below, manually [condition a Bitwarden .csv or .json]({{site.baseurl}}/article/condition-bitwarden-import/).
|
||||
{% endcallout %}
|
||||
|
||||
- [1Password (1pif)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Windows (.sv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Mac (csv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password (1pif)]({{site.baseurl}}/article/import-from-1password/)[1Password (1pif)]({{site.baseurl}}/article/import-from-1password/)[1Password (1pif)]({{site.baseurl}}/article/import-from-1password/)
|
||||
- [1Password 6 & 7 Windows (.sv)]({{site.baseurl}}/article/import-from-1password/)
|
||||
- [1Password 6 & 7 Mac (csv)]({{site.baseurl}}/article/import-from-1password/)
|
||||
- Ascendo DataVault (csv)
|
||||
- Avast Passwords (csv)
|
||||
- Avast Passwords (json)
|
||||
- Avira (json)
|
||||
- BlackBerry Password Keeper (csv)
|
||||
- Blur (csv)
|
||||
- [Brave (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Brave (csv)]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- Buttercup (csv)
|
||||
- [Chrome (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Chrome (csv)]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- Clipperz (html)
|
||||
- Codebook (csv)
|
||||
- Dashlane (json)
|
||||
- Encryptr (csv)
|
||||
- Enpass (csv)
|
||||
- Enpass (json)
|
||||
- [Firefox (csv)]({% link _articles/importing/import-from-firefox.md %})
|
||||
- [Firefox (csv)]({{site.baseurl}}/article/import-from-firefox/)
|
||||
- F-Secure KEY (fsk)
|
||||
- GNOME Passwords and Keys/Seahorse (json)
|
||||
- Kaspersky Password Manager (txt)
|
||||
- KeePass 2 (xml)
|
||||
- KeePassX (csv)
|
||||
- Keeper (csv)
|
||||
- [LastPass (csv)]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- [LastPass (csv)]({{site.baseurl}}/article/import-from-lastpass/)
|
||||
- LogMeOnce (csv)
|
||||
- Meldium (csv)
|
||||
- mSecure (csv)
|
||||
- Myki (csv)
|
||||
- [Microsoft Edge (Chromium) (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Microsoft Edge (Chromium) (csv)]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- Nordpass (csv)
|
||||
- [Opera (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Opera (csv)]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- Padlock (csv)
|
||||
- Passbolt (csv)
|
||||
- PassKeep (csv)
|
||||
@@ -108,6 +108,6 @@ If your format is not listed below, manually [condition a Bitwarden .csv or .jso
|
||||
- Sticky Password (xml)
|
||||
- True Key (csv)
|
||||
- Universal Password Manager (csv)
|
||||
- [Vivaldi (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Vivaldi (csv)]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- Yoti (csv)
|
||||
- Zoho Vault (csv)
|
||||
|
||||
@@ -5,15 +5,15 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 18
|
||||
order: "18"
|
||||
---
|
||||
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Organizations**.
|
||||
|
||||
For more high-level information about **Organizations**, refer to the following articles:
|
||||
- [About Organizations](https://bitwarden.com/help/article/about-organizations/)
|
||||
- [About Collections](https://bitwarden.com/help/article/about-collections/)
|
||||
- [About Groups](https://bitwarden.com/help/article/about-groups/)
|
||||
- [About Organizations]({{site.baseurl}}/article/about-organizations/)
|
||||
- [About Collections]({{site.baseurl}}/article/about-collections/)
|
||||
- [About Groups]({{site.baseurl}}/article/about-groups/)
|
||||
|
||||
## Organizations General
|
||||
|
||||
@@ -37,11 +37,11 @@ Paid Organizations (Families, Teams, or Enterprise) automatically include premiu
|
||||
|
||||
### Q: What events are audited for my Organization?
|
||||
|
||||
**A:** For a full list of what's included in Bitwarden Event Logs, see [Event Logs](https://bitwarden.com/help/article/event-logs/).
|
||||
**A:** For a full list of what's included in Bitwarden Event Logs, see [Event Logs]({{site.baseurl}}/article/event-logs/).
|
||||
|
||||
### Q: Can I prevent users from self-registering into my Organization?
|
||||
|
||||
**A:** If you're self-hosting, [configure the environment variable]({% link _articles/hosting/environment-variables.md %}) `globalSettings__disableUserRegistration=` to `true` to prevent users from signing up for an account via the Registration page. Once configured, Organization Admins or Owners must invite users to signup for an account on the self-hosted instance.
|
||||
**A:** If you're self-hosting, [configure the environment variable]({{site.baseurl}}/article/environment-variables/) `globalSettings__disableUserRegistration=` to `true` to prevent users from signing up for an account via the Registration page. Once configured, Organization Admins or Owners must invite users to signup for an account on the self-hosted instance.
|
||||
|
||||
### Q: My users don't have permission to update desktop apps on their workstations. Can I turn off automatic updates for Bitwarden?
|
||||
|
||||
@@ -78,7 +78,7 @@ Alternatively, you can unshare items by moving them to a different Collection wi
|
||||
|
||||
### Q: How do I hide a password from my Organization's users?
|
||||
|
||||
**A:** Use the **Hide Passwords** option in the **Access Control** section when adding new users or editing existing ones in order to hide a given Collection's passwords and hidden fields from them. For more information, see [Access Control](https://bitwarden.com/help/article/user-types-access-control/#access-control).
|
||||
**A:** Use the **Hide Passwords** option in the **Access Control** section when adding new users or editing existing ones in order to hide a given Collection's passwords and hidden fields from them. For more information, see [Access Control]({{site.baseurl}}/article/user-types-access-control/#access-control).
|
||||
|
||||
### Q: Does an item I move to the Organization stay after I leave?
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: true
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 16
|
||||
order: "16"
|
||||
redirect_from:
|
||||
- /article/change-your-email/
|
||||
---
|
||||
@@ -17,11 +17,11 @@ This article contains Frequently Asked Questions (FAQs) about general Vault Mana
|
||||
|
||||
### Q: What do I do if I forgot my Master Password?
|
||||
|
||||
**A:** As a zero knowledge solution, Bitwarden and its systems have no knowledge of, way to retrieve, or way to reset your Master Password. If you've already lost your Master Password, there is unfortunately no way for the team to recover the account. For help understanding what to do next, or what to do proactively to protect yourself from such a scenario, refer to the article on [Your Master Password]({% link _articles/account/master-password.md %}).
|
||||
**A:** As a zero knowledge solution, Bitwarden and its systems have no knowledge of, way to retrieve, or way to reset your Master Password. If you've already lost your Master Password, there is unfortunately no way for the team to recover the account. For help understanding what to do next, or what to do proactively to protect yourself from such a scenario, refer to the article on [Your Master Password]({{site.baseurl}}/article/master-password/).
|
||||
|
||||
### Q: Is there a way for someone to access my Vault items in case of emergency?
|
||||
|
||||
**A:** There is! Users with a Premium subscription can proactively setup trusted emergency contacts who can access your Vault in case of emergency. For more information, see [Emergency Access]({% link _articles/security/emergency-access.md %}).
|
||||
**A:** There is! Users with a Premium subscription can proactively setup trusted emergency contacts who can access your Vault in case of emergency. For more information, see [Emergency Access]({{site.baseurl}}/article/emergency-access/).
|
||||
|
||||
### Q: How do I change my Master Password hint?
|
||||
|
||||
@@ -48,11 +48,11 @@ When you change your email address, you should immediately logout of all Bitward
|
||||
|
||||
### Q: Why is a Vault item missing from my Mobile App, Desktop App, or Browser Extension?
|
||||
|
||||
**A:** Typically, this is because client application's Vault data has fallen behind a Web Vault or other client application's. Performing a Vault Sync should bring everything up to date. For more information, see [Sync Your Vault]({% link _articles/miscellaneous/vault-sync.md %}).
|
||||
**A:** Typically, this is because client application's Vault data has fallen behind a Web Vault or other client application's. Performing a Vault Sync should bring everything up to date. For more information, see [Sync Your Vault]({{site.baseurl}}/article/vault-sync/).
|
||||
|
||||
### Q: What's the safest way to make a backup of my Vault data?
|
||||
|
||||
**A:** You can use [Encrypted Exports]({% link _articles/importing/encrypted-export.md %}) to make secure long-term backups of your Vault data that are encrypted with your [Account Encryption Key]({% link _articles/account/account-encryption-key.md %}).
|
||||
**A:** You can use [Encrypted Exports]({{site.baseurl}}/article/encrypted-export/) to make secure long-term backups of your Vault data that are encrypted with your [Account Encryption Key]({{site.baseurl}}/article/account-encryption-key/).
|
||||
|
||||
Alternatively, you can use something like PeaZip to create an encrypted archive of the file after exporting a plaintext file from Bitwarden.
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
## Partner Program
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 11
|
||||
order: "11"
|
||||
redirect_from:
|
||||
- /article/why-should-i-trust-bitwarden/
|
||||
- /article/what-happens-if-bitwarden-is-hacked/
|
||||
@@ -20,23 +20,23 @@ This article contains Frequently Asked Questions (FAQs) regarding **Security**.
|
||||
**A:** You can trust us for a few reasons:
|
||||
|
||||
1. Bitwarden is **open source** software. All of our source code is hosted on [GitHub](https://github.com/bitwarden){:target="_blank"} and is free for anyone to review. Thousands of software developers follow Bitwarden's source code projects (and you should too!).
|
||||
2. Bitwarden [is **audited**]({% link _articles/security/is-bitwarden-audited.md %}) **by reputable third-party security firms** as well as independent security researchers.
|
||||
3. Bitwarden **does not store your passwords**. Bitwarden stores encrypted versions of your passwords [that only you can unlock]({% link _articles/security/what-encryption-is-used.md %}). Your sensitive information is encrypted locally on your personal device before ever being sent to our cloud servers.
|
||||
2. Bitwarden [is **audited**]({{site.baseurl}}/article/is-bitwarden-audited/) **by reputable third-party security firms** as well as independent security researchers.[is **audited**]({{site.baseurl}}/article/is-bitwarden-audited/)
|
||||
3. Bitwarden **does not store your passwords**. Bitwarden stores encrypted versions of your passwords [that only you can unlock]({{site.baseurl}}/article/what-encryption-is-used/). Your sensitive information is encrypted locally on your personal device before ever being sent to our cloud servers.
|
||||
4. **Bitwarden has a reputation.** Bitwarden is used by millions of individuals and businesses. If we did anything questionable or risky, we'd be out of business!
|
||||
|
||||
Still don't trust us? You don't have to. Open source is beautiful. You can easily host the entire Bitwarden stack yourself. You control your data. Learn more [here]({% link _articles/hosting/install-on-premise.md %}).
|
||||
Still don't trust us? You don't have to. Open source is beautiful. You can easily host the entire Bitwarden stack yourself. You control your data. Learn more [here]({{site.baseurl}}/article/install-on-premise/).
|
||||
|
||||
### Q: What happens if Bitwarden gets hacked?
|
||||
|
||||
**A:** Bitwarden takes extreme measures to ensure that its websites, applications, and cloud servers are secure. Bitwarden uses Microsoft Azure managed services to manage server infrastructure and security, rather than doing so directly.
|
||||
|
||||
If for some reason Bitwarden were to get hacked and your data was exposed, your information is still protected due to [strong encryption and one-way salted hashing]({% link _articles/security/what-encryption-is-used.md %}) measures taken on your Vault data and master password.
|
||||
If for some reason Bitwarden were to get hacked and your data was exposed, your information is still protected due to [strong encryption and one-way salted hashing]({{site.baseurl}}/article/what-encryption-is-used/) measures taken on your Vault data and master password.
|
||||
|
||||
### Q: Can Bitwarden see my passwords?
|
||||
|
||||
**A:** No.
|
||||
|
||||
Your data is fully encrypted and/or hashed before ever leaving **your** local device, so no one from the Bitwarden team can ever see, read, or reverse engineer to get to your real data. Bitwarden servers only store encrypted and hashed data. For more information about how your data is encrypted, see [Encryption]({% link _articles/security/what-encryption-is-used.md %}).
|
||||
Your data is fully encrypted and/or hashed before ever leaving **your** local device, so no one from the Bitwarden team can ever see, read, or reverse engineer to get to your real data. Bitwarden servers only store encrypted and hashed data. For more information about how your data is encrypted, see [Encryption]({{site.baseurl}}/article/what-encryption-is-used/).
|
||||
|
||||
### Q: Is my Bitwarden master password stored locally?
|
||||
|
||||
@@ -64,7 +64,7 @@ For more information, please visit our [Security and Compliance](https://bitward
|
||||
|
||||
### Q: What third-party services, libraries or identifiers are used in my Bitwarden account?
|
||||
|
||||
**A:** In the Mobile apps, Firebase Cloud Messaging (often mistaken for a tracker) is used only for push notifications related to [sync]({% link _articles/miscellaneous/vault-sync.md %}) and performs absolutely no tracking functions. Microsoft Visual Studio App Center is used for crash reporting on a range of mobile devices. In the Web Vault, Stripe and PayPal scripts are used for payment processing only on payment pages.
|
||||
**A:** In the Mobile apps, Firebase Cloud Messaging (often mistaken for a tracker) is used only for push notifications related to [sync]({{site.baseurl}}/article/vault-sync/) and performs absolutely no tracking functions. Microsoft Visual Studio App Center is used for crash reporting on a range of mobile devices. In the Web Vault, Stripe and PayPal scripts are used for payment processing only on payment pages.
|
||||
|
||||
For those who prefer to exclude all 3rd party communication, Firebase and HockeyApp are removed completely from the F-Droid build. Additionally, Turning off push notifications on a self-hosted Bitwarden server will disable using the push relay server.
|
||||
|
||||
@@ -72,11 +72,11 @@ Bitwarden takes user security and privacy seriously. Bitwarden maintains secure,
|
||||
|
||||
### Q: How do I require Two-step Login for my Bitwarden Organization?
|
||||
|
||||
**A:** Use an [Enterprise Policy]({% link _articles/organizations/policies.md %}), included with an Enterprise Organization subscription. You can also enable Duo MFA integration to enforce 2FA/MFA for your Organization. For more information, see [Two-step Login via Duo]({% link _articles/two-step-login/setup-two-step-login-duo.md %}).
|
||||
**A:** Use an [Enterprise Policy]({{site.baseurl}}/article/policies/), included with an Enterprise Organization subscription. You can also enable Duo MFA integration to enforce 2FA/MFA for your Organization. For more information, see [Two-step Login via Duo]({{site.baseurl}}/article/setup-two-step-login-duo/).
|
||||
|
||||
### Q: What are the certificate options for a self-hosted instance of Bitwarden?
|
||||
|
||||
**A:** See [Certificate Options]({% link _articles/hosting/certificates.md %}) for a complete list and instructions.
|
||||
**A:** See [Certificate Options]({{site.baseurl}}/article/certificates/) for a complete list and instructions.
|
||||
|
||||
### Q: How does Bitwarden vet code changes?
|
||||
|
||||
@@ -88,7 +88,7 @@ Bitwarden takes user security and privacy seriously. Bitwarden maintains secure,
|
||||
|
||||
- Offline Vault sessions will expire after 30 days.
|
||||
- **Except** for mobile client applications, which will expire after 90 days.
|
||||
- [Two-step Login]({{site.baseurl}}/article/setup-two-step-login) **Remember Me** selections will expire after 30 days.
|
||||
- [Two-step Login]({{site.baseurl}}/article/setup-two-step-login/) **Remember Me** selections will expire after 30 days.
|
||||
- Directory Connector [sync cache]({{site.baseurl}}/article/clear-sync-cache/) will be cleared after 30 days.
|
||||
- Organization invites will expire after 5 days. Self-hosted customers can configure this [using an environment variable]({{site.baseurl}}/article/environment-variables/#optional-variables).
|
||||
|
||||
@@ -120,7 +120,7 @@ When this **optional feature** is enabled, clipboard clear will clear any Bitwar
|
||||
### Q: Why does the Browser Extension need `nativeMessaging` permission?
|
||||
|
||||
**A:**
|
||||
Version 1.48.0 of the browser extension enables [Biometric Unlock for Browser Extensions](https://bitwarden.com/help/article/biometrics/#browser-extensions).
|
||||
Version 1.48.0 of the browser extension enables [Biometric Unlock for Browser Extensions]({{site.baseurl}}/article/biometrics/#browser-extensions).
|
||||
|
||||
This permission, also known as `nativeMessaging`, is safe to accept and allows the browser extension to communicate with the Bitwarden desktop app, which is required to enabled Unlock with Biometrics.
|
||||
|
||||
@@ -128,7 +128,7 @@ Note that when your browser updates to this version, you may be asked to accept
|
||||
|
||||
### Q: Is Bitwarden FIPS Compliant?
|
||||
|
||||
**A:** Bitwarden uses [FIPS compliant libraries and cryptography](https://bitwarden.com/help/article/what-encryption-is-used/#invoked-crypto-libraries), however the Bitwarden platform has not performed any FIPs certifications. Most FIPS installations of Bitwarden leverage the self-hosting option to make evaluations (i.e. Cybersecurity Maturity Model Certification) easier.
|
||||
**A:** Bitwarden uses [FIPS compliant libraries and cryptography]({{site.baseurl}}/article/what-encryption-is-used/#invoked-crypto-libraries), however the Bitwarden platform has not performed any FIPs certifications. Most FIPS installations of Bitwarden leverage the self-hosting option to make evaluations (i.e. Cybersecurity Maturity Model Certification) easier.
|
||||
|
||||
### Q: Can I restrict access to Bitwarden to certain devices?
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 09
|
||||
order: "09"
|
||||
---
|
||||
|
||||
### Q: Why can't I create a file Send?
|
||||
@@ -22,11 +22,11 @@ Additionally, creation of file Sends requires your Email Address to be verified.
|
||||
|
||||
### Q: Why are Sends missing from my Send view?
|
||||
|
||||
**A:** By design, Sends are ephemeral. Each created Send has a **maximum lifespan of 31 days**, configurable when you [create a Send]({% link _articles/send/create-send.md %}) or at any time by editing it. When a Send's [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) is reached, it will be purged from Bitwarden systems and inaccessible to both the Sender and any recipients.
|
||||
**A:** By design, Sends are ephemeral. Each created Send has a **maximum lifespan of 31 days**, configurable when you [create a Send]({{site.baseurl}}/article/create-send/) or at any time by editing it. When a Send's [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) is reached, it will be purged from Bitwarden systems and inaccessible to both the Sender and any recipients.
|
||||
|
||||
### Q: What do the icons next to my Sends indicate?
|
||||
|
||||
**A:** Icons in the Send view are intended to help you understand the configured [lifespan]({% link _articles/send/send-lifespan.md %}) and [privacy]({% link _articles/send/send-privacy.md %}) options:
|
||||
**A:** Icons in the Send view are intended to help you understand the configured [lifespan]({{site.baseurl}}/article/send-lifespan/) and [privacy]({{site.baseurl}}/article/send-privacy/) options:
|
||||
|
||||
|Icon|Meaning|
|
||||
|----|-------|
|
||||
@@ -42,10 +42,10 @@ Additionally, creation of file Sends requires your Email Address to be verified.
|
||||
|
||||
During the initial rollout of Send in March 2021, Organizations that already had the [Personal Ownership policy]({{site.baseurl}}/article/policies/#personal-ownership) enabled will find that the Disable Send policy was enabled for their Organizations. This was to allow for customers with this security profile to opt-in to Send on their own schedule.
|
||||
|
||||
If you do want to use Bitwarden Send as an end-to-end encrypted solution for ephemeral sharing within your Organization, all you need to do is turn the Disable Send policy off from the [Business Portal]({% link _articles/organizations/about-business-portal.md %}) or from your Organization's **Manage** → **Policies** page.
|
||||
If you do want to use Bitwarden Send as an end-to-end encrypted solution for ephemeral sharing within your Organization, all you need to do is turn the Disable Send policy off from the [Business Portal]({{site.baseurl}}/article/about-business-portal/) or from your Organization's **Manage** → **Policies** page.
|
||||
|
||||
Learn more about Send [here](https://bitwarden.com/products/send).
|
||||
|
||||
### Q: Can I disable Send for my Organization?
|
||||
|
||||
**A:** Enterprise Organizations can disable Send at any time using the [Disable Send policy]({{site.baseurl}}/article/policies/#disable-send). Admins and Owners can implement this policy from the [Business Portal]({% link _articles/organizations/about-business-portal.md %}) or from your Organization's **Manage** → **Policies** page. Enabling the policy will prevent Organization members from creating or editing any Sends.
|
||||
**A:** Enterprise Organizations can disable Send at any time using the [Disable Send policy]({{site.baseurl}}/article/policies/#disable-send). Admins and Owners can implement this policy from the [Business Portal]({{site.baseurl}}/article/about-business-portal/) or from your Organization's **Manage** → **Policies** page. Enabling the policy will prevent Organization members from creating or editing any Sends.
|
||||
|
||||
@@ -6,13 +6,13 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [sso, enterprise, security]
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Login with SSO**.
|
||||
|
||||
For more high-level information about **Login with SSO**, refer to the following articles:
|
||||
- [Getting Started with Login with SSO](https://bitwarden.com/help/article/getting-started-with-sso/)
|
||||
- [About the Business Portal](https://bitwarden.com/help/article/about-business-portal/)
|
||||
- [Getting Started with Login with SSO]({{site.baseurl}}/article/getting-started-with-sso/)
|
||||
- [About the Business Portal]({{site.baseurl}}/article/about-business-portal/)
|
||||
|
||||
## Using Login with SSO
|
||||
|
||||
@@ -26,7 +26,7 @@ For more high-level information about **Login with SSO**, refer to the following
|
||||
|
||||
### Q: Can I still log in with my Master Password if my Organization has SSO enabled?
|
||||
|
||||
**A:** By default, yes, you can use your email address and Master Password to login to Bitwarden. However, if your Organization enables both the [Single Organization](https://bitwarden.com/help/article/policies/#single-organization) and [Single Sign-On Authentication](https://bitwarden.com/help/article/policies/#single-sign-on-authentication) policies, all non-administrator users will be required to login with SSO.
|
||||
**A:** By default, yes, you can use your email address and Master Password to login to Bitwarden. However, if your Organization enables both the [Single Organization]({{site.baseurl}}/article/policies/#single-organization) and [Single Sign-On Authentication]({{site.baseurl}}/article/policies/#single-sign-on-authentication) policies, all non-administrator users will be required to login with SSO.
|
||||
|
||||
### Q: How does Login with SSO work for new users ("just-in-time")?
|
||||
|
||||
@@ -53,15 +53,15 @@ For more high-level information about **Login with SSO**, refer to the following
|
||||
|
||||
### Q: What plans offer Login with SSO?
|
||||
|
||||
**A:** Only our current Enterprise Plan offers this feature. For more information, see [here](https://bitwarden.com/help/article/2020-plan-updates/).
|
||||
**A:** Only our current Enterprise Plan offers this feature. For more information, see [here]({{site.baseurl}}/article/2020-plan-updates/).
|
||||
|
||||
### Q: How do I upgrade my plan so that I can use Login with SSO?
|
||||
|
||||
**A:** [Contact Us](https://bitwarden.com/contact/) and select **Upgrade/Change Plan** from the **Subject** dropdown menu. We highly recommend you test Login with SSO by starting a [7 Day Enterprise Free Trial](https://bitwarden.com/help/article/enterprise-free-trial).
|
||||
**A:** [Contact Us](https://bitwarden.com/contact/) and select **Upgrade/Change Plan** from the **Subject** dropdown menu. We highly recommend you test Login with SSO by starting a [7 Day Enterprise Free Trial]({{site.baseurl}}/article/enterprise-free-trial/).
|
||||
|
||||
### Q: I would like to test Login with SSO. If I decide I don't need it, can I revert to my Classic 2019 plan?
|
||||
|
||||
**A:** Unfortunately, we aren't able to revert you back to a Classic 2019 plan once you've upgraded. We recommend creating a new Organization to start a [7 Day Enterprise Free Trial](https://bitwarden.com/help/article/enterprise-free-trial/) to test Login with SSO outside of your Primary Organization.
|
||||
**A:** Unfortunately, we aren't able to revert you back to a Classic 2019 plan once you've upgraded. We recommend creating a new Organization to start a [7 Day Enterprise Free Trial]({{site.baseurl}}/article/enterprise-free-trial/) to test Login with SSO outside of your Primary Organization.
|
||||
|
||||
## Supportability
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
This article contains Frequently Asked Questions (FAQs) regarding **Two-step Login**.
|
||||
@@ -17,17 +17,17 @@ This article contains Frequently Asked Questions (FAQs) regarding **Two-step Log
|
||||
|
||||
### Q: Can I require my Organization's users to use Two-step Login?
|
||||
|
||||
**A:** You can require your Organization's users to use Two-step Login by enabling the [Two-step Login Policy]({{site.baseurl}}/article/policies/#two-step-login). Additionally, you can setup [Organization-wide Duo 2FA]({{site.baseurl}}/article/two-step-login-duo) to ensure that all of your users have a secure Two-step Login method at their disposal.
|
||||
**A:** You can require your Organization's users to use Two-step Login by enabling the [Two-step Login Policy]({{site.baseurl}}/article/policies/#two-step-login). Additionally, you can setup [Organization-wide Duo 2FA]({{site.baseurl}}/article/setup-two-step-login-duo/) to ensure that all of your users have a secure Two-step Login method at their disposal.
|
||||
|
||||
### Q: Is FIDO U2F or FIDO2 WebAuthn supported on my iOS or Android App?
|
||||
|
||||
**A:** At this time, due to platform/OS limitations, FIDO is **only supported for Web Vaults, Browser Extensions, and Windows Desktop Apps**, however we are currently investigating ways to implement this. In the meantime, we recommend enabling another [Two-step Login Method]({% link _articles/two-step-login/setup-two-step-login.md %}) for use with unsupported client applications.
|
||||
**A:** Yes! Please see [Two-step Login via FIDO2 WebAuthn]({{site.baseurl}}/article/setup-two-step-login-fido/).
|
||||
|
||||
### Q: Why is Bitwarden not asking for my enabled Two-step Login method?
|
||||
|
||||
**A:** In most cases, one of two things is happening:
|
||||
|
||||
1. You may be already logged in to Bitwarden and only unlocking your Vault. Two-step Login is required to **Log In** but not to **Unlock** your Vault. For more information on the difference between Logging In and Unlocking, see [Vault Timeout Action](https://bitwarden.com/help/article/vault-timeout/#vault-timeout-action).
|
||||
1. You may be already logged in to Bitwarden and only unlocking your Vault. Two-step Login is required to **Log In** but not to **Unlock** your Vault. For more information on the difference between Logging In and Unlocking, see [Vault Timeout Action]({{site.baseurl}}/article/vault-timeout/#vault-timeout-action).
|
||||
|
||||
2. You may have previously checked the **Remember me** checkbox on a device when accessing your Vault using Two-step Login.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [attachments, storage, files]
|
||||
order: 13
|
||||
order: "13"
|
||||
---
|
||||
|
||||
Files can be attached to Vault items from any Bitwarden application. An individual file attachment must be 500 MB (100 MB if uploading from Mobile) or smaller. By default, paid users have access to 1GB of encrypted storage for file attachments. Additional storage can be purchased in 1GB increments.
|
||||
@@ -111,7 +111,7 @@ Use `bw create attachment` to attach a file to an existing Vault item, for exapl
|
||||
bw create attachment --file /path/to/myfile.ext --itemid <itemid>
|
||||
```
|
||||
|
||||
For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more information, refer to our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_sync | markdownify }}
|
||||
|
||||
@@ -5,14 +5,14 @@ categories: [account-management]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [autofill, auto-fill, totp, 2fa, two-step login, two factor authentication, authenticator]
|
||||
order: 12
|
||||
order: "12"
|
||||
---
|
||||
|
||||
The Bitwarden Authenticator is an alternative solution to dedicated authentication apps like Authy, which you can use to verify your identity for websites and apps that use Two-step Login. The Bitwarden Authenticator generates 6-digit [Time-based One-time Passwords](https://en.wikipedia.org/wiki/Time-based_One-time_Password_algorithm) (TOTPs) using SHA-1 and rotates them every 30 seconds.
|
||||
|
||||
{% callout info %}Authenticator key (TOTP) storage is available to all accounts. TOTP code generation requires Premium or membership to a Paid Organization (Families, Teams, or Enterprise).{% endcallout %}
|
||||
|
||||
If you're new to using TOTPs for Two-step Login, refer to the [Field Guide to Two-step Login](https://bitwarden.com/help/article/bitwarden-field-guide-two-step-login/#securing-important-websites) for more information.
|
||||
If you're new to using TOTPs for Two-step Login, refer to the [Field Guide to Two-step Login]({{site.baseurl}}/article/bitwarden-field-guide-two-step-login/#securing-important-websites) for more information.
|
||||
|
||||
## Generate TOTP Codes
|
||||
|
||||
|
||||
@@ -4,14 +4,14 @@ title: Auto-fill Logins on Android
|
||||
categories: [auto-fill]
|
||||
featured: false
|
||||
popular: false
|
||||
order: 02
|
||||
order: "02"
|
||||
tags: [android, autofill, auto-fill]
|
||||
---
|
||||
|
||||
Bitwarden makes your passwords available for auto-fill so that you can seamlessly log in to websites and apps while also maintaining strong and secure passwords. Auto-fill cuts the copying and pasting out of your login routine by detecting Vault items that match the service you're logging in to.
|
||||
|
||||
{% callout success %}
|
||||
*Most* auto-fill scenarios rely on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({% link _articles/features/uri-match-detection.md %}) article.
|
||||
*Most* auto-fill scenarios rely on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({{site.baseurl}}/article/uri-match-detection/) article.
|
||||
|
||||
Please note that custom fields are not currently supported in Mobile auto-fill.
|
||||
{% endcallout %}
|
||||
@@ -29,7 +29,7 @@ Depending on the version of Android your device is running, there are a few diff
|
||||
|
||||
#### Autofill Service
|
||||
|
||||
The Autofill Service (*requires Android 8+*) will overlay a popup when the device is focused on an input that has a [matching Login item]({% link _articles/features/uri-match-detection.md %}). When your Vault is unlocked, you'll be provided the options to immediately auto-fill or to open your Vault:
|
||||
The Autofill Service (*requires Android 8+*) will overlay a popup when the device is focused on an input that has a [matching Login item]({{site.baseurl}}/article/uri-match-detection/). When your Vault is unlocked, you'll be provided the options to immediately auto-fill or to open your Vault:
|
||||
|
||||
{% image features/auto-fill-android/only-autofill-service.png Android Autofill Service%}
|
||||
|
||||
@@ -64,7 +64,7 @@ If your auto-fill overlay doesn't move into your keyboard, check whether the IME
|
||||
|
||||
#### Accessibility
|
||||
|
||||
The Accessibility method will overlap a popup offering to open your Vault to browse [matching Login items]({% link _articles/features/uri-match-detection.md %}) when the device is focused on an input:
|
||||
The Accessibility method will overlap a popup offering to open your Vault to browse [matching Login items]({{site.baseurl}}/article/uri-match-detection/) when the device is focused on an input:
|
||||
|
||||
{% image features/auto-fill-android/drawover.png Accessiblity Popup %}
|
||||
|
||||
@@ -89,7 +89,7 @@ If you're using Android 6+, you must also enable **Draw-Over**.
|
||||
Before you can enable Draw-Over, enable **Accessibility**.
|
||||
{% endcallout %}
|
||||
|
||||
Draw-Over (*required to use Accesibility on Android 6+*) will overlap a popup offering to open your Vault to browse [matching Login items]({% link _articles/features/uri-match-detection.md %}) when the device is focused on an input:
|
||||
Draw-Over (*required to use Accesibility on Android 6+*) will overlap a popup offering to open your Vault to browse [matching Login items]({{site.baseurl}}/article/uri-match-detection/) when the device is focused on an input:
|
||||
|
||||
{% image features/auto-fill-android/drawover.png Accessiblity Popup %}
|
||||
To enable the Draw-Over method:
|
||||
@@ -100,7 +100,7 @@ To enable the Draw-Over method:
|
||||
4. Tap Bitwarden from the list and toggle the **Permit drawing over other apps** option.
|
||||
|
||||
{% callout success %}
|
||||
**Still having problems?** Refer to our break-out guide on [Troubleshooting Android Auto-fill]({% link _articles/miscellaneous/auto-fill-android-troubleshooting.md %}).
|
||||
**Still having problems?** Refer to our break-out guide on [Troubleshooting Android Auto-fill]({{site.baseurl}}/article/auto-fill-android-troubleshooting/).
|
||||
|
||||
If you're still not able to get Android auto-fill working, [Contact Us](https://bitwarden.com/contact){:target="\_blank"}.
|
||||
{% endcallout %}
|
||||
|
||||
@@ -4,14 +4,14 @@ title: Auto-fill Logins in Browser Extensions
|
||||
categories: [auto-fill]
|
||||
featured: false
|
||||
popular: false
|
||||
order: 01
|
||||
order: "01"
|
||||
tags: [browser, auto-fill, autofill]
|
||||
---
|
||||
|
||||
{% callout success %}
|
||||
Most auto-fill functionality relies on the attribution of URIs to Login items. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
Most auto-fill functionality relies on the attribution of URIs to Login items. If you're unfamiliar with using URIs, see [Using URIs]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
Additionally, **basic authentication prompts** work a little differently than regular auto-fills. See our breakout article on [Basic Auth Prompts]({{site.baseurl}}/article/basic-auth-autofill)
|
||||
Additionally, **basic authentication prompts** work a little differently than regular auto-fills. See our breakout article on [Basic Auth Prompts]({{site.baseurl}}/article/basic-auth-autofill/)
|
||||
{% endcallout %}
|
||||
|
||||
Bitwarden Browser Extensions have a unique **Tab** view, which automatically detects the URI (e.g. `myturbotax.intuit.com`) of the page displayed in the open tab and surfaces any Vault items with corresponding URIs.
|
||||
@@ -53,7 +53,7 @@ To auto-fill login information, use the following **default** shortcuts. If ther
|
||||
- On Linux: `Ctrl + Shift + L`
|
||||
|
||||
{% callout success %}
|
||||
If a login uses the [Bitwarden Authenticator]({% link _articles/features/authenticator-keys.md %}) for TOTPs, using the `Cmd/Ctrl + Shift + L` will automatically copy your TOTP to your clipboard after auto-filling. All you have to do is `Cmd/Ctrl + V` to paste!
|
||||
If a login uses the [Bitwarden Authenticator]({{site.baseurl}}/article/authenticator-keys/) for TOTPs, using the `Cmd/Ctrl + Shift + L` will automatically copy your TOTP to your clipboard after auto-filling. All you have to do is `Cmd/Ctrl + V` to paste!
|
||||
{% endcallout %}
|
||||
|
||||
If any given shortcut doesn't work, it's likely because another application on your device is already registered to use it. For example, the auto-fill shortcut on Windows is commonly claimed by the AMD Radeon Adrenaline software (AMD graphic drivers) and therefore cannot be used by Bitwarden. In these instances, you should free up the shortcut or configure Bitwarden to use a different shortcut.
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
layout: article
|
||||
title: Auto-fill Cards & Identities
|
||||
categories: [auto-fill]
|
||||
order: 04
|
||||
order: "04"
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [browser, autofill, auto-fill, identity, card, form fill]
|
||||
---
|
||||
|
||||
Bitwarden can do more than just [auto-fill your usernames and passwords]({% link _articles/features/auto-fill-browser.md %})! **Bitwarden Browser Extensions** can auto-fill [Cards]({{site.baseurl}}/article/managing-items/#cards) and [Identities]({{site.baseurl}}/article/managing-items/#identities) to simplify online purchases, account creation, and more using the [unique Tab view]({% link _articles/features/auto-fill-browser.md %}).
|
||||
Bitwarden can do more than just [auto-fill your usernames and passwords]({{site.baseurl}}/article/auto-fill-browser/)! **Bitwarden Browser Extensions** can auto-fill [Cards]({{site.baseurl}}/article/managing-items/#cards) and [Identities]({{site.baseurl}}/article/managing-items/#identities) to simplify online purchases, account creation, and more using the [unique Tab view]({{site.baseurl}}/article/auto-fill-browser/).
|
||||
|
||||
{% callout info %}Currently, Autofill for Cards & Identities is **only available for Browser Extensions**. Mobile platforms including Android and iOS do not currently support this type of auto-fill function.{% endcallout %}
|
||||
|
||||
@@ -18,7 +18,7 @@ To auto-fill Cards and Identities:
|
||||
|
||||
1. Open the Browser Extension or, if your Browser Extension is already open, navigate to the {% icon fa-folder %} **Tab** view.
|
||||
|
||||
Unless you've [hidden Cards and/or Identities from this view](#hide-cards--identities), all your Cards and Identities will be listed here alongside any [matched Login items]({% link _articles/features/uri-match-detection.md %}).
|
||||
Unless you've [hidden Cards and/or Identities from this view](#hide-cards--identities), all your Cards and Identities will be listed here alongside any [matched Login items]({{site.baseurl}}/article/uri-match-detection/).
|
||||
2. Select the Card or Identity you want to auto-fill:
|
||||
|
||||
{% image features/auto-fill-card-id/autofill-cardsidentities.png Auto-fill an Identity %}
|
||||
|
||||
@@ -4,14 +4,14 @@ title: Auto-fill Logins on iOS
|
||||
categories: [auto-fill]
|
||||
featured: true
|
||||
popular: false
|
||||
order: 03
|
||||
order: "03"
|
||||
tags: [iOS, Auto-fill, autofill]
|
||||
---
|
||||
|
||||
Bitwarden makes your passwords available for auto-fill so that you can seamlessly log in to websites and apps while also maintaining strong and secure passwords. Auto-fill cuts the copying and pasting out of your login routine by detecting Vault items that match the service you're logging in to.
|
||||
|
||||
{% callout success %}
|
||||
*Most* auto-fill scenarios rely on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({% link _articles/features/uri-match-detection.md %}) article.
|
||||
*Most* auto-fill scenarios rely on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({{site.baseurl}}/article/uri-match-detection/) article.
|
||||
|
||||
Please note that custom fields are not currently supported in Mobile auto-fill.
|
||||
{% endcallout %}
|
||||
@@ -24,7 +24,7 @@ Auto-fill on iOS comes in two flavors:
|
||||
- **Browser App Extension**: Use this option to make Bitwarden auto-fill accessible *only* in Web Browser apps, like Safari, through the Share menu.
|
||||
|
||||
{% callout success %}
|
||||
It is currently not possible to use auto-fill on iOS if the [Vault Timeout Action]({{site.baseurl}}/article/vault-timeout/#vault-timeout-action) for the device is set to **Log Out** and your *only* enabled [Two-step Login Method]({{site.baseurl}}/article/setup-two-step-login) requires NFC (e.g. an NFC YubiKey), as iOS will not allow NFC inputs to interrupt auto-fill workflows.
|
||||
It is currently not possible to use auto-fill on iOS if the [Vault Timeout Action]({{site.baseurl}}/article/vault-timeout/#vault-timeout-action) for the device is set to **Log Out** and your *only* enabled [Two-step Login Method]({{site.baseurl}}/article/setup-two-step-login/) requires NFC (e.g. an NFC YubiKey), as iOS will not allow NFC inputs to interrupt auto-fill workflows.
|
||||
|
||||
Either change your Vault Timeout Action to **Lock**, or enable another Two-step Login Method.
|
||||
{% endcallout %}
|
||||
@@ -48,7 +48,7 @@ To enable keyboard auto-fill on iOS:
|
||||
|
||||
{% image features/auto-fill-ios/autofill-ios.jpeg AutoFill on iOS %}
|
||||
|
||||
If a [matching Login]({% link _articles/features/uri-match-detection.md %}) is displayed, tap it to auto-fill. If the {% icon fa-key %} **Passwords** button is displayed, tap it to browse your Vault for the Login item to use. In cases where the {% icon fa-key %} **Passwords** button is displayed, it's probably because there isn't an item in your Vault with a [matching URI]({% link _articles/features/uri-match-detection.md %}).
|
||||
If a [matching Login]({{site.baseurl}}/article/uri-match-detection/) is displayed, tap it to auto-fill. If the {% icon fa-key %} **Passwords** button is displayed, tap it to browse your Vault for the Login item to use. In cases where the {% icon fa-key %} **Passwords** button is displayed, it's probably because there isn't an item in your Vault with a [matching URI]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
{% callout info %}Are you getting a `Biometric unlock disabled pending verification of master password` message? [Learn what to do]({{site.baseurl}}/article/autofill-faqs/#q-what-do-i-do-about-biometric-unlock-disabled-pending-verification-of-master-password).{% endcallout%}
|
||||
|
||||
@@ -70,7 +70,7 @@ To enable Browser App Extension auto-fill on iOS:
|
||||
|
||||
{% image features/auto-fill-ios/extension.png Bitwarden in the Share menu %}
|
||||
|
||||
{% callout info %}If you have [Unlock with Biometrics]({% link _articles/account/biometrics.md %}) enabled, the first time you tap this option you will be prompted to verify your Master Password.{% endcallout %}
|
||||
8. A Bitwarden screen will slide up on your device and will list [matching Login items]({% link _articles/features/uri-match-detection.md %}) for the website. Tap the item to auto-fill.
|
||||
{% callout info %}If you have [Unlock with Biometrics]({{site.baseurl}}/article/biometrics/) enabled, the first time you tap this option you will be prompted to verify your Master Password.{% endcallout %}[Unlock with Biometrics]({{site.baseurl}}/article/biometrics/)
|
||||
8. A Bitwarden screen will slide up on your device and will list [matching Login items]({{site.baseurl}}/article/uri-match-detection/) for the website. Tap the item to auto-fill.
|
||||
|
||||
{% callout success %}If there are no Login items listed, it's probably because there isn't an item in your Vault with a [matching URI]({% link _articles/features/uri-match-detection.md %}).{% endcallout %}
|
||||
{% callout success %}If there are no Login items listed, it's probably because there isn't an item in your Vault with a [matching URI]({{site.baseurl}}/article/uri-match-detection/).{% endcallout %}
|
||||
|
||||
@@ -4,7 +4,7 @@ title: Blacklisting URIs
|
||||
categories: [auto-fill]
|
||||
featured: false
|
||||
popular: false
|
||||
order: 06
|
||||
order: "06"
|
||||
tags: [android, autofill, auto-fill]
|
||||
---
|
||||
|
||||
@@ -12,7 +12,7 @@ tags: [android, autofill, auto-fill]
|
||||
Blacklisting URIs is currently only available for Bitwarden Mobile on **Android 8.0 (Oreo)** or higher.
|
||||
{% endcallout %}
|
||||
|
||||
Auto-fill relies on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({% link _articles/features/uri-match-detection.md %}) article. **Android** users can explicitly blacklist URIs to prevent Bitwarden from offering them for auto-fill. To specify URIs to blacklist:
|
||||
Auto-fill relies on the attribution of URIs to Login items. If you're unfamiliar with using URIs, brush up using our [Using URIs]({{site.baseurl}}/article/uri-match-detection/) article. **Android** users can explicitly blacklist URIs to prevent Bitwarden from offering them for auto-fill. To specify URIs to blacklist:
|
||||
|
||||
1. In the Bitwarden Android app, open the {% icon fa-cog %} **Settings** tab.
|
||||
2. Tap **Options**.
|
||||
|
||||
@@ -5,69 +5,44 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [fields, autofill, custom fields]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
Custom fields, available for any [Vault item type]({% link _articles/account/managing-items.md %}), allow you to store additional well-structured data fields for a Vault item. Custom fields are saved as `Name:Value` pairs, and can be one of three types:
|
||||
Custom fields, available for any [Vault item type]({{site.baseurl}}/article/managing-items/), allow you to store additional well-structured data fields for a Vault item. Custom fields are saved as `Name:Value` pairs, and can be one of three types:
|
||||
|
||||
- **Text**: Field value stores a freeform input (text, numbers, etc.)
|
||||
- **Hidden**: Field value stores freeform input that is hidden from view (particularly useful for Organizations using the [Hide Password access control](https://bitwarden.com/help/article/user-types-access-control/#granular-access-control)).
|
||||
- **Hidden**: Field value stores freeform input that is hidden from view (particularly useful for Organizations using the [Hide Password access control]({{site.baseurl}}/article/user-types-access-control/#granular-access-control)).
|
||||
- **Boolean**: Field value stores a boolean value (true/false).
|
||||
|
||||
## Custom Fields for Keys
|
||||
{% callout success %}
|
||||
#### Custom Fields for Keys
|
||||
|
||||
In addition to common web service inputs like PINs and Security Questions, Custom Fields can be used to store values **up to 5000 characters in length**, for example RSA 4096-bit SSH keys.
|
||||
|
||||
{% callout success %}
|
||||
Character limits for custom field values are imposed on the **post-encryption character count**. For example, a 3383-character RSA-4096 Private SSH key would grow to about 4400-characters when it's encrypted and stored in your Vault.
|
||||
{% endcallout %}
|
||||
|
||||
## Auto-fill Custom Fields
|
||||
## Creating Custom Fields
|
||||
|
||||
The **Name** specified for a custom field is critical to successfully setting up auto-fill for custom fields. When naming the custom field, you should use one of the following HTML form element attributes/values:
|
||||
Custom fields can be added to a Vault item from any Bitwarden client using the **Custom Fields** section of the **Edit Item** panel:
|
||||
|
||||
1. HTML form element's `id` attribute.
|
||||
2. HTML form element's `name` attribute.
|
||||
3. HTML form element's corresponding `label` value.
|
||||
4. HTML form element's `aria-label` attribute.
|
||||
5. HTML form element's `placeholder` attribute.
|
||||
{% image features/custom-fields.png Custom Fields in Web Vault %}
|
||||
|
||||
Bitwarden will search the matched-URI webpage for those HTML form element attributes/values **in the above priority-order**. If a custom field's name matches one of those attributes/values, its value can be auto-filled into the HTML form element.
|
||||
### Custom Field Names
|
||||
|
||||
### Name to Attribute Matching
|
||||
The specified **Name** is important to get right in order to successfully auto-fill a custom field. Using the Browser Extension, you can quickly get the correct field name using the **Copy Custom Field Name** option in the context menu (in most cases, by right-clicking on the form element):
|
||||
|
||||
Field Name to attribute/value matches is an **exact** and **case-insensitive** comparison. For example, if your custom field has the name `PIN`:
|
||||
{% image features/custom-fields-contextmenu.png %}
|
||||
|
||||
- **Auto-fill offered** for `pin`, `PiN`, `PIN`, etc.
|
||||
- **Auto-fill not offered** for `pin2` or `mypin`
|
||||
Selecting this context menu option will copy the form element's `id`, `name`, `aria-label`, or `placeholder` value (**in that order of preference**).
|
||||
|
||||
### Field Name Prefixing
|
||||
#### Find Custom Field Names Manually
|
||||
|
||||
There are two cases in which you can exercise more control over [name to attribute mapping](#name-to-attribute-mapping) by using prefixes.
|
||||
If you don't use the Browser Extension, the best way to find a field name is to use your web browser's developer tools, as in the following example:
|
||||
|
||||
#### csv
|
||||
{% image features/custom-fields/custom_field.gif Browser Extension Context Menu %}
|
||||
|
||||
Prefixing your custom field's name with `csv=` allows you to specify multiple names to search for and compare to when auto-fill is performed. For example:
|
||||
|
||||
`csv=pin,pin2,mypin` will offer auto-fill for all the above examples.
|
||||
|
||||
#### regex
|
||||
|
||||
Prefixing your custom field's name with `regex=` allows you to perform [regular expression comparisons](https://regexone.com/){:target="_blank"} when auto-fill is performed. For example:
|
||||
|
||||
`regex=pin` will offer auto-fill for all the above examples.
|
||||
|
||||
`regex=^first.*name` will offer auto-fill for `firstName`, `First_name`, and `First Name`
|
||||
|
||||
### Example Auto-fill Configuration
|
||||
|
||||
Follow this procedure to correctly configure a custom field for auto-fill. This example uses Google Chrome for its Developer Tools.
|
||||
|
||||
{% image features/custom-fields/custom_field.gif %}
|
||||
|
||||
1. On the webpage that matches the Login item's URI, right-click the field you want to auto-fill to and select **Inspect**.
|
||||
|
||||
The HTML element will open and be highlighted in the Developer Console.
|
||||
1. On the webpage that matches the Login item's URI, right-click the field you want to auto-fill to and select **Inspect**. The HTML element will open and be highlighted in the Developer Console.
|
||||
2. Find and copy the element `id` (find `id="xxx"`, where `xxx` is the element's `id` value).
|
||||
3. In the relevant Vault item's **Custom Fields** section, choose the appropriate field type and select the {% icon fa-plus %} **New Custom Field** button:
|
||||
|
||||
@@ -77,3 +52,28 @@ Follow this procedure to correctly configure a custom field for auto-fill. This
|
||||
|
||||
{% image features/custom-fields/custom-field-eg.png Custom field example %}
|
||||
6. Save the Vault item.
|
||||
|
||||
### More About Custom Field Names
|
||||
|
||||
#### Order of Preference
|
||||
|
||||
If you're naming a custom field manually, you should use one of the following HTML form element attributes/values **in order of preference**:
|
||||
|
||||
1. HTML form element's `id` attribute.
|
||||
2. HTML form element's `name` attribute.
|
||||
3. HTML form element's `aria-label` attribute.
|
||||
4. HTML form element's `placeholder` attribute.
|
||||
|
||||
#### Matching
|
||||
|
||||
Field name matching is an **exact** and **case-insensitive** comparison. For example, if your custom field has the name `PIN`:
|
||||
|
||||
- **Auto-fill is offered** for `pin`, `PiN`, `PIN`, etc.
|
||||
- **Auto-fill is not offered** for `pin2` or `mypin`
|
||||
|
||||
#### Prefixing
|
||||
|
||||
There are two cases in which you can exercise more control over [matching](#matching) by using prefixes:
|
||||
|
||||
- **csv**: Prefixing your custom field's name with `csv=` allows you to specify multiple names to search for and compare against for auto-fill, for example `csv=pin,mypin,pincode`.
|
||||
- **regex**: Prefixing your custom field's name with `regex=` allows you to perform [regular expression comparisons](https://regexone.com){:target="\_blank"} when auto-fill is performed. For example, `regex=^first.*name` will offer auto-fill for `firstName`, `First_name`, and `First Name`.
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: true
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
If you're new to Bitwarden, it's likely that the web browser you use has been saving and auto-filling your passwords. Most web browsers enable this by default, but experts generally agree that [built-in password managers are more vulnerable](https://www.wired.com/2016/08/browser-password-manager-probably-isnt-enough/){:target="\_blank"} than dedicated solutions like Bitwarden.
|
||||
@@ -69,7 +69,7 @@ You should also find out which Logins Firefox has already saved by selecting the
|
||||
|
||||
{% image features/firefox-delete.png Firefox Saved Logins %}
|
||||
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/article/import-from-firefox) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/article/import-from-firefox/) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
|
||||
{% endcapture %}
|
||||
{{ firefox | markdownify }}
|
||||
|
||||
@@ -5,12 +5,12 @@ categories: [account-management]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [favorites, features, tutorial]
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
|
||||
Any item can be designated as a **Favorite** allow quick access to your most used items.
|
||||
|
||||
Even items [shared with you from an Organization]({% link _articles/organizations/sharing.md %}) can be designated a Favorite, but this will only impact how they appear in your Personal Vault (i.e. you won't make that item a Favorite for other users with access to the Organization or Collection).
|
||||
Even items [shared with you from an Organization]({{site.baseurl}}/article/sharing/) can be designated a Favorite, but this will only impact how they appear in your Personal Vault (i.e. you won't make that item a Favorite for other users with access to the Organization or Collection).
|
||||
|
||||
{% callout success %}
|
||||
Items marked as a **Favorite** will appear at the top of your {% icon fa-lock %} **My Vault** view in Browser Extensions and Mobile Apps, and in the {% icon fa-star %} **Favorites** filter in your Web Vault and Desktop Apps.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [security]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [fingerprint]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Each Bitwarden account has a public "fingerprint phrase" associated with it. Your account's fingerprint phrase is permanent and composed of five random english words that appear in a specific order, for example:
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [categories, folders, sub-folders]
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
Folders are structures used to organize your Personal Vault by gathering together Logins, Cards, Identities, and Secure Notes. Using Folders is a great way to make all Vault items easy to find. Any Vault item can be added to a Folder, including [items shared with you from an Organization]({{site.baseurl}}/article/sharing/).
|
||||
@@ -98,7 +98,7 @@ To create a Folder, use the command:
|
||||
bw create folder <foldername>
|
||||
```
|
||||
|
||||
You can edit an existing folder using `bw edit <folderId>` and delete one using `bw delete folder <folderId>`. For more information, refer to our [CLI documentation]({{site.baseurl}}/article/cli).
|
||||
You can edit an existing folder using `bw edit <folderId>` and delete one using `bw delete folder <folderId>`. For more information, refer to our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
@@ -116,7 +116,7 @@ There are similarities between Folders and Collections. **Folders organize your
|
||||
Folders can be "nested" in order to logically organize them within your Vault. There's no limit to the depth with which you can nest Folders, but creating too many levels may interfere with your Vault's interface.
|
||||
|
||||
{% callout info %}
|
||||
Searching inside a "parent" Folder will not include items in Folders nested inside it as potential search results. For more information, see [Search your Vault]({% link _articles/features/searching-vault.md %}).
|
||||
Searching inside a "parent" Folder will not include items in Folders nested inside it as potential search results. For more information, see [Search your Vault]({{site.baseurl}}/article/searching-vault/).
|
||||
{% endcallout %}
|
||||
|
||||
{% image manage-items/subfolders.png Nested folders %}
|
||||
@@ -213,7 +213,7 @@ Using `edit` will require you to:
|
||||
- Manipulate the JSON object (specifically, the `folderId` attribute) with a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"}.
|
||||
- Use the `encode` command to encode changes to the JSON object.
|
||||
|
||||
If you're unfamiliar with using any of these parts, refer to our [CLI documentation]({{site.baseurl}}/article/cli).
|
||||
If you're unfamiliar with using any of these parts, refer to our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
{% endcallout %}
|
||||
|
||||
{% endcapture %}
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [account, report, breach, reused, unsecured, weak]
|
||||
order: 15
|
||||
order: "15"
|
||||
---
|
||||
|
||||
Vault Health Reports can be used to evaluate the security of your Bitwarden Personal or Organization Vault.
|
||||
@@ -60,7 +60,7 @@ Once identified, you should use Bitwarden's Password Generator to create a stron
|
||||
|
||||
### Unsecured Websites Report
|
||||
|
||||
The **Unsecured Websites Report** identifies Login items that use unsecured (`http://`) schemes in URIs. It's much safer to use `https://` to encrypt communications with TLS/SSL. To learn more, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
The **Unsecured Websites Report** identifies Login items that use unsecured (`http://`) schemes in URIs. It's much safer to use `https://` to encrypt communications with TLS/SSL. To learn more, see [Using URIs]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
Once identified, you should change offending URIs from `http://` to `https://`.
|
||||
|
||||
@@ -91,5 +91,5 @@ Once you have the key, open your `./bwdata/env/global.override.env` and REPLACE
|
||||
globalSettings__hibpApiKey=REPLACE
|
||||
```
|
||||
|
||||
For more information, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %}).
|
||||
For more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|
||||
{% endcallout %}
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [search, lunr]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Bitwarden Vaults can be easily searched to quickly surface relevant Vault items. [Basic search](#basic-search) queries can be made in any Bitwarden client application, and advanced [full-text search](#full-text-search) queries can be made in Web Vaults, Desktop Apps, and Browser Extensions.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [auto-fill]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [uri, match detection, autofill]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Any Login item in your Vault can be created with or edited to include one or more URI (Uniform Resource Identifier). A URI can be a website address (i.e. a URL), a Server IP Address, a Mobile App Package ID, and more.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [getting-started]
|
||||
featured: true
|
||||
popular: true
|
||||
tags: [getting started, create account]
|
||||
order: 01
|
||||
order: "01"
|
||||
---
|
||||
## Welcome to Bitwarden
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [tutorial, getting started, browser extensions]
|
||||
order: 03
|
||||
order: "03"
|
||||
---
|
||||
|
||||
Bitwarden Browser Extensions integrate password management directly into your favorite browser. Download a Bitwarden Browser Extension from your browser's marketplace or app store, or from the [Bitwarden Downloads](https://bitwarden.com/download){:target="\_blank"} page.
|
||||
@@ -14,7 +14,7 @@ Bitwarden Browser Extensions integrate password management directly into your fa
|
||||
Browser Extensions are supported for the two most recent versions of **Google Chrome**, **Mozilla Firefox**, **Opera**, **Microsoft Edge**, and **Safari**. For **Vivaldi**, **Brave**, and **Tor**, only the most recent version is supported.
|
||||
|
||||
{% callout success %}
|
||||
**The Safari Browser Extension is packaged with the Desktop Application**, available for download from the App Store. For more information, see [Safari App Extension]({% link _articles/account/install-safari-app-extension.md %}).
|
||||
**The Safari Browser Extension is packaged with the Desktop Application**, available for download from the App Store. For more information, see [Safari App Extension]({{site.baseurl}}/article/install-safari-app-extension/).
|
||||
{% endcallout %}
|
||||
|
||||
{% image getting-started/browserext/browserext-vault.png Bitwarden Browser Extension in Google Chrome %}
|
||||
@@ -43,7 +43,7 @@ Organizing your Vault into **Favorites** and **Folders** makes navigating your V
|
||||
3. Select a **Folder** from the dropdown to add this item to a folder, or check the **Favorite** checkbox to add it to your Favorites.
|
||||
4. Select **Save** in the top-right corner of the Browser Extension.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
## Add a Login
|
||||
|
||||
@@ -51,7 +51,7 @@ Any time you log in to a website that doesn't already have a Login item saved fo
|
||||
|
||||
{% image getting-started/browserext/browserext-add.png %}
|
||||
|
||||
Selecting **Yes, Save Now** will automatically add a Login item to your Vault with the entered username, password, and URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
Selecting **Yes, Save Now** will automatically add a Login item to your Vault with the entered username, password, and [URI]({% link _articles/features/uri-match-detection.md %}). You can also use the **Select folder...** dropdown to select which [Folder]({{site.baseurl}}/article/folders/) to save this item to.
|
||||
|
||||
{% callout success %}
|
||||
You can disable this banner by selecting the **Disable Add Login Notification** option from the **Options** menu in your Browser Extension.
|
||||
@@ -59,7 +59,7 @@ You can disable this banner by selecting the **Disable Add Login Notification**
|
||||
|
||||
## Launch a Website
|
||||
|
||||
You can launch a website directly from the Bitwarden Browser Extension by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
You can launch a website directly from the Bitwarden Browser Extension by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
{% image getting-started/browserext/browserext-launch.png %}
|
||||
|
||||
@@ -73,7 +73,7 @@ When a Vault item has a corresponding URI, the Bitwarden icon will overlay a not
|
||||
|
||||
Simply clicking on the Vault item inside the Browser Extension will auto-fill login information to the detected input fields.
|
||||
|
||||
There are a few other methods of auto-filling login information from your Browser Extension, including context menus and keyboard shortcuts. To learn about them, see [Browser Extension Auto-fill Options]({% link _articles/features/auto-fill-browser.md %}).
|
||||
There are a few other methods of auto-filling login information from your Browser Extension, including context menus and keyboard shortcuts. To learn about them, see [Browser Extension Auto-fill Options]({{site.baseurl}}/article/auto-fill-browser/).
|
||||
|
||||
## Unlock with PIN / Biometrics
|
||||
|
||||
@@ -85,7 +85,7 @@ For lightening fast access to your credentials, setup a PIN or Biometrics to unl
|
||||
|
||||
{% callout success%}**Optional:** The pre-check option **Lock with master password on browser restart** will require you to enter your Master Password instead of a PIN when your browser restarts. If you want to be able to unlock with a PIN when you browser restarts, uncheck this option.{% endcallout %}
|
||||
|
||||
For more information, see [Unlock with PIN]({% link _articles/account/unlock-with-pin.md %}) or [Unlock with Biometrics]({% link _articles/account/biometrics.md %}).
|
||||
For more information, see [Unlock with PIN]({{site.baseurl}}/article/unlock-with-pin/) or [Unlock with Biometrics]({{site.baseurl}}/article/biometrics/).
|
||||
|
||||
## Pin an Extension
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [tutorial, getting started, desktop, windows, mac, linux]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Bitwarden's Desktop App brings a full Vault experience straight out of your browser and into your desktop. Using a 3-column layout, the Bitwarden Desktop App is designed to help you quickly locate the Vault item you want to use or edit:
|
||||
@@ -53,7 +53,7 @@ Organizing your Vault into **Favorites** and **Folders** makes filtering your Va
|
||||
3. Select a **Folder** from the dropdown to add this item to a folder, or check the **Favorite** checkbox to add it to your Favorites.
|
||||
4. Select the {% icon fa-save %} **Save** icon.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Create New Logins
|
||||
|
||||
@@ -121,7 +121,7 @@ Organizing your Vault into **Favorites** and **Folders** makes filtering your Va
|
||||
3. Select a **Folder** from the dropdown to add this item to a folder, or check the **Favorite** checkbox to add it to your Favorites.
|
||||
4. Select the {% icon fa-save %} **Save** icon.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Create New Logins
|
||||
|
||||
@@ -187,7 +187,7 @@ Organizing your Vault into **Favorites** and **Folders** makes filtering your Va
|
||||
3. Select a **Folder** from the dropdown to add this item to a folder, or check the **Favorite** checkbox to add it to your Favorites.
|
||||
3. Select the {% icon fa-save %} **Save** icon.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Create New Logins
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [tutorial, getting started, mobile, android, ios]
|
||||
order: 04
|
||||
order: "04"
|
||||
redirect_from:
|
||||
- /article/getting-started-android/
|
||||
- /article/getting-started-ios/
|
||||
@@ -56,7 +56,7 @@ Organizing your Vault into **Favorites** and **Folders** makes navigating your V
|
||||
3. Tap **Folder** to select a folder for this item, or toggle the **Favorite** switch to add it to your Favorites.
|
||||
3. Tap **Save** in the top-right corner of your screen.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Create New Logins
|
||||
|
||||
@@ -65,7 +65,7 @@ You can create new Logins, Cards, Identities, and Secure Notes directly from any
|
||||
1. In your Bitwarden Android app, tap the {% icon fa-plus %} Add icon in the bottom-right corner.
|
||||
2. Choose which **Type** of item to create (for example, *Login*).
|
||||
3. Enter all the information for the item (for example, *Username* and *Password*).
|
||||
4. For Logins, enter the website the login is used for in the **URI** field (for example, [www.amazon.com](##create-items)).
|
||||
4. For Logins, enter the website the login is used for in the **URI** field (for example, `www.amazon.com`).
|
||||
5. Tap **Folder** or toggle the **Favorite** switch to sort the item in your Vault.
|
||||
6. When you're finished, tap **Save** in the top-right corner of your screen.
|
||||
|
||||
@@ -82,11 +82,11 @@ Setup Auto-fill to automatically enter logins from your Android device to a Web
|
||||
Depending on which version of Android you're using, a number of Auto-fill options could be listed.
|
||||
2. Tap your available Auto-fill option, and toggle it on. A green `Enabled` message will indicate that Auto-fill is active.
|
||||
|
||||
Once toggled, you might be required to change some Android-native settings, depending on your available or enabled Auto-fill options. For more information, see [Auto-fill logins on Android]({% link _articles/features/auto-fill-android.md %}).
|
||||
Once toggled, you might be required to change some Android-native settings, depending on your available or enabled Auto-fill options. For more information, see [Auto-fill logins on Android]({{site.baseurl}}/article/auto-fill-android/).
|
||||
|
||||
### Launch from Mobile Apps
|
||||
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
{% image getting-started/mobile-launch.png %}
|
||||
|
||||
@@ -152,7 +152,7 @@ Organizing your Vault into **Favorites** and **Folders** makes navigating your V
|
||||
3. Tap **Folder** to select a folder for this item, or toggle the **Favorite** switch to add it to your Favorites.
|
||||
3. Tap **Save** in the top-right corner of your screen.
|
||||
|
||||
For more information, see [Folders]({% link _articles/features/folders.md %}) and [Favorites]({% link _articles/features/favorites.md %}).
|
||||
For more information, see [Folders]({{site.baseurl}}/article/folders/) and [Favorites]({{site.baseurl}}/article/favorites/).
|
||||
|
||||
### Create New Logins
|
||||
|
||||
@@ -161,7 +161,7 @@ You can create new Logins, Cards, Identities, and Secure Notes directly from any
|
||||
1. Tap the {% icon fa-plus %} Add icon in the top-right corner.
|
||||
2. Choose which **Type** of item to create (for example, *Login*).
|
||||
3. Enter all the information for the item (for example, *Username* and *Password*).
|
||||
4. For Logins, enter the website the login is used for in the **URI** field (for example, [www.amazon.com](#)).
|
||||
4. For Logins, enter the website the login is used for in the **URI** field (for example, `www.amazon.com`).
|
||||
5. Tap **Folder** or toggle the **Favorite** switch to organize the item in your Vault.
|
||||
6. When you're finished, tap **Save** in the top-right corner of your screen.
|
||||
|
||||
@@ -183,7 +183,7 @@ When you create new logins, make sure you enter a website in the [URI field](#cr
|
||||
|
||||
### Launch from Mobile Apps
|
||||
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({{site.baseurl}}/article/uri-match-detection/).
|
||||
|
||||
{% image getting-started/mobile-launch.png %}
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [tutorial]
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
## Why Bitwarden Organizations?
|
||||
@@ -119,7 +119,7 @@ Confirm accepted Organization to complete the loop:
|
||||
3. Select any `Accepted` users and use the {% icon fa-cog %} gear dropdown to {% icon fa-check %} **Confirm Selected**:
|
||||
|
||||
{% image organizations/org-people-options-overlay.png Confirm an Accepted user %}
|
||||
3. Verify that the [fingerprint phrase]({{site.baseurl}}/article/fingerprint-phrase) on your screen matches the one your new member can find in **Settings** → **My Account**:
|
||||
3. Verify that the [fingerprint phrase]({{site.baseurl}}/article/fingerprint-phrase/) on your screen matches the one your new member can find in **Settings** → **My Account**:
|
||||
|
||||
{% image fingerprint-phrase.png Sample Fingerprint Phrase %}
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: true
|
||||
tags: [getting started, videos, bitwarden 101]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
## Bitwarden 101 - Getting Started
|
||||
|
||||
@@ -6,16 +6,16 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [tutorial, getting started, web vault]
|
||||
order: 02
|
||||
order: "02"
|
||||
---
|
||||
|
||||
**The Bitwarden Web Vault provides the richest Bitwarden experience** for personal users and Organizations. Lots of important functions, like setting up [Two-step Login]({% link _articles/two-step-login/setup-two-step-login.md %}) or administering an [Organization]({% link _articles/organizations/about-organizations.md %}), can only be done from the Web Vault.
|
||||
**The Bitwarden Web Vault provides the richest Bitwarden experience** for personal users and Organizations. Lots of important functions, like setting up [Two-step Login]({{site.baseurl}}/article/setup-two-step-login/) or administering an [Organization]({{site.baseurl}}/article/about-organizations/), can only be done from the Web Vault.
|
||||
|
||||
Your Web Vault is accessible from any modern web browser by navigating to [vault.bitwarden.com](https://vault.bitwarden.com){:target=\_blank}.
|
||||
|
||||
{% image getting-started/webvault.png The Bitwarden Web Vault %}
|
||||
|
||||
When your first log in to your Web Vault, you'll land on the **My Vault** view. This space will list all your Vault items, including Logins, Cards, Identities, and Secure Notes. To learn about these different types of items, see [Vault Items]({% link _articles/account/managing-items.md %}).
|
||||
When your first log in to your Web Vault, you'll land on the **My Vault** view. This space will list all your Vault items, including Logins, Cards, Identities, and Secure Notes. To learn about these different types of items, see [Vault Items]({{site.baseurl}}/article/managing-items/).
|
||||
|
||||
## First Steps
|
||||
|
||||
@@ -30,7 +30,7 @@ To create a folder:
|
||||
1. Select the {% icon fa-plus %} plus icon next to the Folders section in your Filters column.
|
||||
2. Enter a Name (e.g. `Social Media Logins`) for your folder and select **Save**.
|
||||
|
||||
{% callout success %}For added organizational prowess, you can nest folders inside other folders. To learn how, see [Folders]({% link _articles/features/folders.md %}).{% endcallout %}
|
||||
{% callout success %}For added organizational prowess, you can nest folders inside other folders. To learn how, see [Folders]({{site.baseurl}}/article/folders/).{% endcallout %}
|
||||
|
||||
#### Add a Login
|
||||
|
||||
@@ -40,7 +40,7 @@ To add a new Login item:
|
||||
2. Make sure that **Login** is selected from the type dropdown (if you're adding a Card, Identity, or Secure Note instead, select that type).
|
||||
3. Enter a **Name** for the item. Names are used to help you easily identify an item in your Vault, so give it a recognizable one (e.g. `My Twitter Login`).
|
||||
4. Enter your **Username** and **Password** for the Login item. For now, enter your **existing** password, we'll help you [replace it with a stronger password](#generate-a-strong-password) later.
|
||||
5. We always recommend adding something to the **URI 1** field so that you can auto-fill your Login from your [mobile app]({% link _articles/getting-started/getting-started-mobile.md %}) or [browser extension]({% link _articles/getting-started/getting-started-browserext.md %}).
|
||||
5. We always recommend adding something to the **URI 1** field so that you can auto-fill your Login from your [mobile app]({{site.baseurl}}/article/getting-started-mobile/) or [browser extension]({{site.baseurl}}/article/getting-started-browserext/).
|
||||
|
||||
For most Login items, this should be the URL a webpage (e.g. `https://twitter.com/login`). If you don't know what URL to use, navigate to the website's login screen and copy it from your address bar.
|
||||
|
||||
@@ -77,13 +77,13 @@ Now that a new Login item is saved in your Vault, you can beef up its security b
|
||||
|
||||
Do you have usernames and passwords saved somewhere else, for instance in a web browser like Google Chrome or another password manager like LastPass?
|
||||
|
||||
**Good news!** In your Web Vault, you can import credentials to Bitwarden in-bulk rather than having to manually create a new item for each. To learn how, use our guide on [Importing Data to your Vault]({% link _articles/importing/import-data.md %}).
|
||||
**Good news!** In your Web Vault, you can import credentials to Bitwarden in-bulk rather than having to manually create a new item for each. To learn how, use our guide on [Importing Data to your Vault]({{site.baseurl}}/article/import-data/).
|
||||
|
||||
## Setup Two-step Login
|
||||
|
||||
Besides using a really good [Master Password]({% link _articles/account/master-password.md %}), using Two-step Login is the best measure you can take to protect your Vault. Two-step Login requires that you verify your identity upon logging in to your account using an additional "token", typically retrieved from a different device.
|
||||
Besides using a really good [Master Password]({{site.baseurl}}/article/master-password/), using Two-step Login is the best measure you can take to protect your Vault. Two-step Login requires that you verify your identity upon logging in to your account using an additional "token", typically retrieved from a different device.
|
||||
|
||||
There are many [available methods]({% link _articles/two-step-login/setup-two-step-login.md %}) for Two-step Login, but the recommended method for a free Bitwarden account is using a mobile device authenticator app like [Authy](https://authy.com/){:target="\_blank"}:
|
||||
There are many [available methods]({{site.baseurl}}/article/setup-two-step-login/) for Two-step Login, but the recommended method for a free Bitwarden account is using a mobile device authenticator app like [Authy](https://authy.com/){:target="\_blank"}:
|
||||
|
||||
1. Download Authy on your mobile device.
|
||||
2. In your Bitwarden Web Vault, navigate to the **Settings** tab from the top navigation bar.
|
||||
@@ -111,8 +111,8 @@ Congratulations on mastering the basics of Bitwarden! We want everyone to be saf
|
||||
|
||||
For personal users, we offer a premium subscription for **$10 / year** that unlocks advanced Vault capabilities including:
|
||||
|
||||
- Advanced Two-step Login options, like [Duo]({% link _articles/two-step-login/setup-two-step-login-duo.md %}) and [YubiKey Security Keys]({% link _articles/two-step-login/setup-two-step-login-yubikey.md %})
|
||||
- Storage space for [Encrypted File Attachments]({% link _articles/features/attachments.md %})
|
||||
- Advanced Two-step Login options, like [Duo]({{site.baseurl}}/article/setup-two-step-login-duo/) and [YubiKey Security Keys]({{site.baseurl}}/article/setup-two-step-login-yubikey/)[Duo]({{site.baseurl}}/article/setup-two-step-login-duo/)[Duo]({{site.baseurl}}/article/setup-two-step-login-duo/)[Duo]({{site.baseurl}}/article/setup-two-step-login-duo/)[Duo]({{site.baseurl}}/article/setup-two-step-login-duo/)
|
||||
- Storage space for [Encrypted File Attachments]({{site.baseurl}}/article/attachments/)[Encrypted File Attachments]({{site.baseurl}}/article/attachments/)[Encrypted File Attachments]({{site.baseurl}}/article/attachments/)[Encrypted File Attachments]({{site.baseurl}}/article/attachments/)
|
||||
- A built-in [Temporary One-time Password (TOTP) Authenticator]({% link _articles/features/authenticator-keys.md %})
|
||||
- [Emergency Access]({% link _articles/security/emergency-access.md %}) to your Vault by trusted emergency contacts
|
||||
- [Vault Health Reports]({% link _articles/features/reports.md %}) that report on password and security hygiene
|
||||
@@ -126,6 +126,6 @@ To start a premium subscription:
|
||||
|
||||
Do you need to share passwords or other Vault items with your friends, family, team, or entire business?
|
||||
|
||||
Bitwarden Organizations let you do just that. We recommend trying out the functionality of password-sharing from Organizations by starting a **free** 2-person Organization. To learn how, see [Get Started with an Organization]({% link _articles/getting-started/getting-started-organizations.md %}).
|
||||
Bitwarden Organizations let you do just that. We recommend trying out the functionality of password-sharing from Organizations by starting a **free** 2-person Organization. To learn how, see [Get Started with an Organization]({{site.baseurl}}/article/getting-started-organizations/).
|
||||
|
||||
Once you've tested an Organization, check out our [Bitwarden Plans and Pricing](https://bitwarden.com/pricing/business/) page to learn about the different Paid Organizations you might consider.
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [project guide, poc]
|
||||
order: 05
|
||||
order: "05"
|
||||
redirect_from:
|
||||
- /article/bitwarden-proof-of-concept-project-guide/
|
||||
---
|
||||
@@ -21,12 +21,12 @@ This guide is designed by our Product, Implementation, and Sales specialists at
|
||||
|1|(**Self-hosting only**) Install Bitwarden|Organization Owner / IT Team|Setup your Bitwarden server. We recommend deploying on Linux for optimal performance and lowest total cost of ownership.|[Install and Deploy]({{site.baseurl}}/article/install-on-premise/)|2.5|
|
||||
|1|Add Admins|Organization Owners + Admins|Onboard [Admins]({{site.baseurl}}/article/user-types-access-control/) to Bitwarden, who can manage *most* Organization structures. We also recommend adding a second Owner for redundancy.|[User Management]({{site.baseurl}}/article/managing-users/)|0.2|
|
||||
|2|Create Collections|Organization Owners + Admins|Create [Collections]({{site.baseurl}}/article/about-collections/), which gather items for secure sharing with Groups of users.|[Collections]({{site.baseurl}}/article/about-collections/)|0.25|
|
||||
|2| Create Groups|Organization Owners + Admins|Create [Groups]({{site.baseurl}}/article/about-groups), which gather users for scalable assignment of permissions and access to Collections.<br><br>If you decide to sync Groups and users from your Identity Provider or Directory Service, you may need to reconfigure user and Group assignments later.|[Groups]({{site.baseurl}}/article/groups/)|0.25|
|
||||
|2| Create Groups|Organization Owners + Admins|Create [Groups]({{site.baseurl}}/article/about-groups/), which gather users for scalable assignment of permissions and access to Collections.<br><br>If you decide to sync Groups and users from your Identity Provider or Directory Service, you may need to reconfigure user and Group assignments later.|[Groups]({{site.baseurl}}/article/groups/)|0.25|
|
||||
|2|Assign Groups to Collections|Organization Owners + Admins| Assign Groups to Collections, making shared items available to supersets of users. Test the *Read Only* and *Hide Password* options.|[Collections Assignment]({{site.baseurl}}/article/about-groups/#edit-collections-assignments)|.5|
|
||||
|2|Share items to Collections|Organization Owners + Admins|[Add items manually]({{site.baseurl}}/article/sharing/#create-an-organization-item) or [import data]({{site.baseurl}}/article/import-to-org/) from another password management application.|[Sharing]({{site.baseurl}}/article/sharing)<br><br>[Import to an Organization]({{site.baseurl}}/article/import-to-org/)|0.25|
|
||||
|2|Share items to Collections|Organization Owners + Admins|[Add items manually]({{site.baseurl}}/article/sharing/#create-an-organization-item) or [import data]({{site.baseurl}}/article/import-to-org/) from another password management application.|[Sharing]({{site.baseurl}}/article/sharing/)<br><br>[Import to an Organization]({{site.baseurl}}/article/import-to-org/)|0.25|
|
||||
|2|Configure Enterprise Policies|Organization Owners + Admins|Enterprise Policies can be used to tailor your Bitwarden Organization to fit your security needs. **Enable and configure desired policies before user onboarding begins.**|[Enterprise Policies]({{site.baseurl}}/article/policies/)|0.1|
|
||||
|3|Add users to Groups|Organization Owners + Admins|Add a set of users to your Organization manually and assign them to different groups. With these users, you'll broadly test all pre-configured functionality **in the next step**, before moving on to advanced functions like Directory Connector.|[User Management]({{site.baseurl}}/article/managing-users/)<br><br>[Groups]({{site.baseurl}}/article/about-groups/)|0.5|
|
||||
|3|Download Bitwarden Client Applications|All users|All Organization members should download Bitwarden on an assortment of devices, login, and test access to shared items/Collections/Groups and application of applied Policies. **If you're self-hosting,** users will need to [connect each client to your server]({{site.baseurl}}/article/change-client-environment).|[Download Bitwarden](https://get.bitwarden.com/)|0.5|
|
||||
|3|Download Bitwarden Client Applications|All users|All Organization members should download Bitwarden on an assortment of devices, login, and test access to shared items/Collections/Groups and application of applied Policies. **If you're self-hosting,** users will need to [connect each client to your server]({{site.baseurl}}/article/change-client-environment/).|[Download Bitwarden](https://get.bitwarden.com/)|0.5|
|
||||
|4-6|Configure Login with SSO|Organization Owners + Admins|Configure Bitwarden to authenticate using your SAML 2.0 or OIDC Identity Provider.|[About Login with SSO]({{site.baseurl}}/article/about-sso/)|1.5|
|
||||
|4-6|Configure and test user onboarding with Directory Connector|Organization Owners + Admins|Download, configure, and test the Bitwarden Directory Connector application, which is used to automatically sync users and groups from your existing directory service (LDAP, AD, etc.)|[About Directory Connector]({{site.baseurl}}/article/directory-sync/)|1.5|
|
||||
|4-6|Configure Directory Connector for production onboarding|Organization Owners + Admins|Execute on using Directory Connector to invite your remaining users to the Organization.|[Directory Connector Desktop App]({{site.baseurl}}/article/directory-sync-desktop/)|1|
|
||||
@@ -38,8 +38,8 @@ We've seen a lot of deployments and have found that taking the following actions
|
||||
|Day|Action|Key Person|Description|Resource(s)|Duration (hrs)|
|
||||
|:-:|:----:|:--------:|:---------:|:---------:|:------------:|
|
||||
|4-6|Determine timeline for rollout to first-wave users|Senior Leadership & Security teams|There are lots of different strategies for rolling out Bitwarden. Take things at whatever pace best suits your team.| | |
|
||||
|7|Craft internal messaging about Bitwarden rollout|Internal Training & Managers|Bitwarden provides a lot of resources to help users quickly adopt, check some out on [Youtube](http://youtube.com/bitwarden) and on the [Help Center](https://bitwarden.com/help/).|[Youtube](http://youtube.com/bitwarden)<br><br>[Help Center](https://bitwarden.com/help/)||
|
||||
|7|Communicate to internal leaders about Password Management policies|Internal leaders / Security teams|Make sure your teams know about any [Enterprise Policies]({{site.baseurl}}/article/policies), [2FA]({{site.baseurl}}/article/setup-two-step-login-duo/) or [SSO]({{site.baseurl}}/article/about-sso/) requirements, and password management best practices.| | |
|
||||
|7|Craft internal messaging about Bitwarden rollout|Internal Training & Managers|Bitwarden provides a lot of resources to help users quickly adopt, check some out on [Youtube](http://youtube.com/bitwarden) and on the [Help Center]({{site.baseurl}}/article/).|[Youtube](http://youtube.com/bitwarden)<br><br>[Help Center](https://bitwarden.com/help)||
|
||||
|7|Communicate to internal leaders about Password Management policies|Internal leaders / Security teams|Make sure your teams know about any [Enterprise Policies]({{site.baseurl}}/article/policies/), [2FA]({{site.baseurl}}/article/setup-two-step-login-duo/) or [SSO]({{site.baseurl}}/article/about-sso/) requirements, and password management best practices.| | |
|
||||
| | | | | | |
|
||||
| | | | |**Total Hours (Cloud-hosted)**|**7.35**|
|
||||
| | | | |**Total Hours (Self-hosted)**|**9.85**|
|
||||
|
||||
@@ -25,6 +25,16 @@ Bitwarden believes source code transparency is an absolute requirement for secur
|
||||
|
||||
To be notified of Release Announcements, subscribe to the [Bitwarden Status RSS Feed](https://status.bitwarden.com/){:target="\_blank"}.
|
||||
|
||||
## 2021-09-21
|
||||
|
||||
The latest release of Bitwarden focuses on often requested improvements to existing functionality:
|
||||
|
||||
- **FIDO2 WebAuthn on Mobile**: Two-step Login via FIDO2 WebAuthn is now supported on iOS and Android (see [here]({{site.baseurl}}/article/setup-two-step-login-fido/) for details).
|
||||
- **Admin Password Reset - Automatic Enrollment Improvement**: The Automatic Enrollment policy option will now prevent users from withdrawing from Admin Password Reset (see [here]({{site.baseurl}}/article/admin-reset/#automatic-enrollment) for details).
|
||||
- **Browser Extension - Select Folder from Save Bar**: You can now select which [Folder]({{site.baseurl}}/article/folders) to save an item to directly from the Browser Extension's save prompt (see [here]({{site.baseurl}}/article/getting-started-browserext/#add-a-login) for details).
|
||||
- **Browser Extension - Custom Field Context Menu Item**: You can now copy an HTML element name directly from the Browser Extension's context menu for easy custom field creation (see [here]({{site.baseurl}}/article/custom-fields/#custom-field-names) for details).
|
||||
- **CAPTCHA Validation**: Starting with this release, we're turning on [hCaptcha](https://www.hcaptcha.com/about){:target="\_blank"} validation to protect against bot attacks like credential stuffing. Please note, challenges in the CLI are delivered differently than in other client applications (see [here]({{site.baseurl}}/article/cli-auth-challenges/) for CLI details).
|
||||
|
||||
## 2021-08-18
|
||||
|
||||
{% callout success %}
|
||||
@@ -84,18 +94,18 @@ Prior to 5/15/2021, we recommend digging through your Trash for anything you mig
|
||||
|
||||
Bitwarden is proud to announce the release of Bitwarden Send, and end-to-end encrypted solution for ephemeral sharing. This release includes:
|
||||
|
||||
- **Bitwarden Send**: Bitwarden Send is end-to-end encrypted solution for ephemeral sharing. There's lot of material about Send on our website and Help Center, but you can start [here](https://bitwarden.com/products/send){:target="\_blank"} or [here]({% link _articles/send/about-send.md %}).
|
||||
- **FIDO U2F Support for Edge**: Two-step Login via FIDO U2F is now available for the Web Vault and Browser Extensions in Microsoft Edge (see [here]({% link _articles/two-step-login/setup-two-step-login-fido.md %}) for details).
|
||||
- **Domain Exclusion in Browser Extensions**: Bitwarden Browser Extensions can now be configured with domains to explicitly not offer to remember passwords for (see [here]({% link _articles/miscellaneous/exclude-domains.md %}) for details).
|
||||
- **Bitwarden Send**: Bitwarden Send is end-to-end encrypted solution for ephemeral sharing. There's lot of material about Send on our website and Help Center, but you can start [here](https://bitwarden.com/products/send){:target="\_blank"} or [here]({{site.baseurl}}/article/about-send/).
|
||||
- **FIDO U2F Support for Edge**: Two-step Login via FIDO U2F is now available for the Web Vault and Browser Extensions in Microsoft Edge (see [here]({{site.baseurl}}/article/setup-two-step-login-fido/) for details).
|
||||
- **Domain Exclusion in Browser Extensions**: Bitwarden Browser Extensions can now be configured with domains to explicitly not offer to remember passwords for (see [here]({{site.baseurl}}/article/exclude-domains/) for details).
|
||||
- **Improved Import Error Messages**: We've had lots of folks migrating to Bitwarden recently, so we cleaned up an import error message to help you reconcile issues faster (see [here]({{site.baseurl}}/article/import-data/#length-related-import-errors) for details).
|
||||
- **Safari Web Extension Port**: Our Safari App Extension has officially been ported to a Web Extension for use with Safari 14+. Due to changes to Safari, Web Extension use is now limited to only those obtained through Mac App Store downloads (see [here]({% link _articles/account/install-safari-app-extension.md %}) for details).
|
||||
- **Safari Web Extension Port**: Our Safari App Extension has officially been ported to a Web Extension for use with Safari 14+. Due to changes to Safari, Web Extension use is now limited to only those obtained through Mac App Store downloads (see [here]({{site.baseurl}}/article/install-safari-app-extension/) for details).
|
||||
|
||||
## 2021-01-19 Post-Release Update
|
||||
|
||||
{% callout info %}
|
||||
Biometric Unlock for Browser Extensions is available for **only Chromium-based browsers** (e.g. Chrome, Edge) with v1.48.0 of the Browser Extension, provided you have the latest version (2021-01-19) of the Desktop App.
|
||||
|
||||
When your Browser Extension updates to this version, you may be asked to accept a new permission for Bitwarden to `Communicate with cooperating native applications`. This permission is safe, but **optional**, and will enable the Browser Extension to communicate with the Bitwarden Desktop App, which is required to enable Biometric Unlock (see [here](https://bitwarden.com/help/article/biometrics/#browser-extensions) for details). Declining this permission will allow you to use v1.48.0 without Biometric Unlock functionality.
|
||||
When your Browser Extension updates to this version, you may be asked to accept a new permission for Bitwarden to `Communicate with cooperating native applications`. This permission is safe, but **optional**, and will enable the Browser Extension to communicate with the Bitwarden Desktop App, which is required to enable Biometric Unlock (see [here]({{site.baseurl}}/article/biometrics/#browser-extensions) for details). Declining this permission will allow you to use v1.48.0 without Biometric Unlock functionality.
|
||||
|
||||
**Biometric Unlock is currently not available for:**
|
||||
- Firefox Browser Extensions below version 87.
|
||||
@@ -107,29 +117,29 @@ The Bitwarden team is investigating these and will provide updates as things pro
|
||||
|
||||
## 2021-01-19
|
||||
For the first major release of 2021, the Bitwarden team combined multiple major enhancements to address the critical needs of all users, including:
|
||||
- **Emergency Access**: Bitwarden's new Emergency Access feature enables users to designate and manage trusted emergency contacts, who may request access to their Vault in a zero knowledge environment (see [here]({% link _articles/security/emergency-access.md %}) for details).
|
||||
- **Encrypted Exports**: Personal users and Organizations can now export Vault data in an encrypted `.json` file (see [here]({% link _articles/importing/encrypted-export.md %}) for details).
|
||||
- **New Role**: A Custom role is now available to allow for granular control over user permissions (see [here](https://bitwarden.com/help/article/user-types-access-control/#custom-role) for details).
|
||||
- **New Enterprise Policy**: The Personal Ownership policy is now available for use by Enterprise Organization (see [here](https://bitwarden.com/help/article/policies/#personal-ownership) for details).
|
||||
- **Biometric Unlock for Browser Extensions**: Using an integration with a native Desktop application, you can now use Biometric input to unlock Chromium-based Browser Extensions (see [here](https://bitwarden.com/help/article/biometrics/#browser-extensions) for details).
|
||||
- **Emergency Access**: Bitwarden's new Emergency Access feature enables users to designate and manage trusted emergency contacts, who may request access to their Vault in a Zero Knowledge/Zero Trust environment (see [here]({{site.baseurl}}/article/emergency-access/) for details).[here]({{site.baseurl}}/article/emergency-access/)
|
||||
- **Encrypted Exports**: Personal users and Organizations can now export Vault data in an encrypted `.json` file (see [here]({{site.baseurl}}/article/encrypted-export/) for details).
|
||||
- **New Role**: A Custom role is now available to allow for granular control over user permissions (see [here]({{site.baseurl}}/article/user-types-access-control/#custom-role) for details).
|
||||
- **New Enterprise Policy**: The Personal Ownership policy is now available for use by Enterprise Organization (see [here]({{site.baseurl}}/article/policies/#personal-ownership) for details).
|
||||
- **Biometric Unlock for Browser Extensions**: Using an integration with a native Desktop application, you can now use Biometric input to unlock Chromium-based Browser Extensions (see [here]({{site.baseurl}}/article/biometrics/#browser-extensions) for details).
|
||||
|
||||
## 2020-11-12
|
||||
The latest release of Bitwarden adds SSO-related enhancements to all client applications, including:
|
||||
- **New Enterprise Policies:** The Single Organization and Single Sign-On Authentication polices are now available for use by Enterprise Organizations (see [here](https://bitwarden.com/help/article/policies/) for details).
|
||||
- **API Key for CLI:** Authenticate into the Bitwarden CLI using an API Key newly available from your Web Vault (see [here](https://bitwarden.com/help/article/personal-api-key/) for details).
|
||||
- **New Enterprise Policies:** The Single Organization and Single Sign-On Authentication polices are now available for use by Enterprise Organizations (see [here]({{site.baseurl}}/article/policies/) for details).
|
||||
- **API Key for CLI:** Authenticate into the Bitwarden CLI using an API Key newly available from your Web Vault (see [here]({{site.baseurl}}/article/personal-api-key/) for details).
|
||||
- **Improvements to SSO Onboarding:** We've made some improvements to the way users are onboarded via SSO to prevent potential security risks (see [here](https://github.com/bitwarden/server/pull/945) for details).
|
||||
- **GDPR Acknowledgement:** From now on, new users of Bitwarden will be asked to acknowledge a Privacy Policy on registration.
|
||||
- **Android 11 Inline Auto-fill**: For devices using Android 11+, enabling the Auto-fill Service will display suggestions inline for IMEs that also support [this feature](https://developer.android.com/guide/topics/text/ime-autofill#workflow) (see [here](https://github.com/bitwarden/mobile/pull/1145) for details).
|
||||
|
||||
## 2020-9-30
|
||||
The latest release of Bitwarden adds much-anticipated **Login with SSO** functionality for all client applications, and the Business Portal for Web Vaults. Read this [blog post](https://bitwarden.com/blog/post/bitwarden-launches-sso-authentication/) for more information about Login with SSO, and refer to our [documentation](https://bitwarden.com/help/login-with-sso).
|
||||
The latest release of Bitwarden adds much-anticipated **Login with SSO** functionality for all client applications, and the Business Portal for Web Vaults. Read this [blog post](https://bitwarden.com/blog/post/bitwarden-launches-sso-authentication/) for more information about Login with SSO, and refer to our [documentation]({{site.baseurl}}/article/login-with-sso/).
|
||||
|
||||
## Early 2020 releases
|
||||
|
||||
The following items were released between March and September of 2020.
|
||||
|
||||
- [Enterprise Policies](https://bitwarden.com/help/article/policies/)
|
||||
- [Vault Timeout Options](https://bitwarden.com/help/article/vault-timeout/)
|
||||
- [Trash functionality](https://bitwarden.com/help/article/managing-items/#deleting-an-item)
|
||||
- [Password View Permissions - "Hide Passwords"](https://bitwarden.com/help/article/user-types-access-control/#granular-access-control)
|
||||
- [Touch ID / Windows Hello for Desktop Applications](https://bitwarden.com/help/article/biometrics/#desktop-applications)
|
||||
- [Enterprise Policies]({{site.baseurl}}/article/policies/)
|
||||
- [Vault Timeout Options]({{site.baseurl}}/article/vault-timeout/)
|
||||
- [Trash functionality]({{site.baseurl}}/article/managing-items/#deleting-an-item)
|
||||
- [Password View Permissions - "Hide Passwords"]({{site.baseurl}}/article/user-types-access-control/#granular-access-control)
|
||||
- [Touch ID / Windows Hello for Desktop Applications]({{site.baseurl}}/article/biometrics/#desktop-applications)
|
||||
|
||||
@@ -5,13 +5,13 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, admin]
|
||||
order: 09
|
||||
order: "09"
|
||||
---
|
||||
|
||||
The Bitwarden System Administrator Portal can be used to:
|
||||
|
||||
- Check currently installed and latest available versions.
|
||||
- View Environment Configuration settings (for more information, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %})).
|
||||
- View Environment Configuration settings (for more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/)).
|
||||
- View and delete registered users.
|
||||
- View and delete registered Organizations.
|
||||
|
||||
@@ -33,7 +33,7 @@ These email addresses **do not** need to be registered with an account on your B
|
||||
|
||||
### Configure SMTP Mail Server
|
||||
|
||||
The System Adminstrator Portal uses email to provide secure links for authentication. Therefore, you will need to configure your installation's SMTP Mail Server settings prior to attempting to log in to the portal. For more information, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %}).
|
||||
The System Adminstrator Portal uses email to provide secure links for authentication. Therefore, you will need to configure your installation's SMTP Mail Server settings prior to attempting to log in to the portal. For more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|
||||
|
||||
## Access the Admin Portal
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, backup]
|
||||
order: 07
|
||||
order: "07"
|
||||
---
|
||||
|
||||
When self-hosting Bitwarden, you are responsible for implementing your own backup procedures in order to keep data safe.
|
||||
@@ -14,7 +14,7 @@ When self-hosting Bitwarden, you are responsible for implementing your own backu
|
||||
|
||||
Bitwarden's Docker containers use volume mapping to persist all important data on the host machine, meaning stopping your containers will not delete any data. Docker containers, on the other hand, are to be considered ephemeral and do not persist data or state.
|
||||
|
||||
All Bitwarden data is stored on the host machine in the `./bwdata` directory, relative to the location in which you installed Bitwarden. For more information, see [Install and Deploy](https://bitwarden.com/help/article/install-on-premise/#install-bitwarden).
|
||||
All Bitwarden data is stored on the host machine in the `./bwdata` directory, relative to the location in which you installed Bitwarden. For more information, see [Install and Deploy]({{site.baseurl}}/article/install-on-premise/#install-bitwarden).
|
||||
|
||||
## Backup Hosted Data
|
||||
|
||||
|
||||
@@ -5,10 +5,10 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, install, deploy]
|
||||
order: 04
|
||||
order: "04"
|
||||
---
|
||||
|
||||
This article defines the certificate options available to Self-hosted instances of Bitwarden. You will select your certificate option during installation. For installation instructions, see [Install and Deploy On-premise]({% link _articles/hosting/install-on-premise.md %}).
|
||||
This article defines the certificate options available to Self-hosted instances of Bitwarden. You will select your certificate option during installation. For installation instructions, see [Install and Deploy On-premise]({{site.baseurl}}/article/install-on-premise/).
|
||||
|
||||
## Generate a Certificate with Let's Encrypt
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, environment]
|
||||
order: 11
|
||||
order: "11"
|
||||
---
|
||||
|
||||
By default, Bitwarden client applications (Browser Extensions, Mobile Apps, etc.) will connect to Bitwarden-hosted servers. Client applications can be configured to connect to your self-hosted Bitwarden instance.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 10
|
||||
order: "10"
|
||||
---
|
||||
|
||||
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.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, install, deploy]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Some features of Bitwarden are not configured by the `bitwarden.sh` installer. Configure these settings by editing the environment file, located at `./bwdata/env/global.override.env`. `global.override.env` comes pre-baked with configurable variables (see [Included Variables](#included-variables)), however there are additional variables which can be manually added (see [Optional Variables](#optional-variables)).
|
||||
@@ -35,7 +35,7 @@ The following variables are among those that already exist in `global.override.e
|
||||
|globalSettings__mail__smtp__password=|A valid password for the `smtp__host`.|
|
||||
|globalSettings__disableUserRegistration=|Specify `true` to disable new users signing up for an account on this instance via the Registration page.|
|
||||
|globalSettings__hibpApiKey=|Your HaveIBeenPwned (HIBP) API Key, available [here](https://haveibeenpwned.com/API/Key).|
|
||||
|adminSettings__admins=|Email addresses which may access the [System Administrator Portal]({% link _articles/hosting/admin-portal.md%}).|
|
||||
|adminSettings__admins=|Email addresses which may access the [System Administrator Portal]({{site.baseurl}}/article/admin-portal/).|
|
||||
|
||||
## Optional Variables
|
||||
|
||||
|
||||
@@ -5,10 +5,10 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, database, mssql]
|
||||
order: 12
|
||||
order: "12"
|
||||
---
|
||||
|
||||
By default, self-hosted instances of Bitwarden will use a Microsoft SQL Server (MSSQL) database created as a normal part of [installation setup]({{site.baseurl}}/article/install-on-premise), however you configure Bitwarden to use an external MSSQL database.
|
||||
By default, self-hosted instances of Bitwarden will use a Microsoft SQL Server (MSSQL) database created as a normal part of [installation setup]({{site.baseurl}}/article/install-on-premise/), however you configure Bitwarden to use an external MSSQL database.
|
||||
|
||||
{% callout info %}
|
||||
Currently, self-hosted installations of Bitwarden support **only** MSSQL databases. Stay tuned for future updates on this topic.
|
||||
|
||||
@@ -5,9 +5,9 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, install, deploy]
|
||||
order: 02
|
||||
order: "02"
|
||||
---
|
||||
This article will walk you through the procedure to manually install and deploy Bitwarden to your own server. **Installation using the Bitwarden installation script is recommended for most users, for instructions see [Install and Deploy]({% link _articles/hosting/install-on-premise.md %})**.
|
||||
This article will walk you through the procedure to manually install and deploy Bitwarden to your own server. **Installation using the Bitwarden installation script is recommended for most users, for instructions see [Install and Deploy]({{site.baseurl}}/article/install-on-premise/)**.
|
||||
|
||||
A manual installation may be appropriate if you are intimately familiar with Docker technologies and desire more control over your Bitwarden installation.
|
||||
|
||||
@@ -88,7 +88,7 @@ Complete the following steps to install Bitwarden manually:
|
||||
9. Replace the domain placeholder in `./web/app-id.json` with your domain name.
|
||||
10. Configure your Environment Variables in `./env/global.override.env`.
|
||||
|
||||
At a minimum, we recommend configuring you SMTP Mail Server and Admin Portal Access. For more information, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %}).
|
||||
At a minimum, we recommend configuring you SMTP Mail Server and Admin Portal Access. For more information, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|
||||
|
||||
11. Map the desired user and group id for the Bitwarden containers to run under at `./env/uid.env`. For example:
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, install, deploy]
|
||||
order: 01
|
||||
order: "01"
|
||||
---
|
||||
|
||||
This article will walk you through the procedure to install and deploy Bitwarden to your own server. Bitwarden can be installed and deployed on Linux, macOS, and Windows machines.
|
||||
@@ -33,7 +33,7 @@ The following is a summary of the Installation Procedure in this article. Links
|
||||
2. [**Install Docker and Docker Compose**](#install-docker-and-docker-compose) on your machine, and complete the optional [**Docker Post-Installation**](#docker-post-installation-linux-only).
|
||||
3. Retrieve an installation id and key from [**https://bitwarden.com/host**](https://bitwarden.com/host){:target="_blank"} for use in installation.
|
||||
|
||||
For more information, see [What are my installation id and installation key used for?](https://bitwarden.com/help/article/hosting-faqs/#general).
|
||||
For more information, see [What are my installation id and installation key used for?]({{site.baseurl}}/article/hosting-faqs/#general).
|
||||
4. [**Install Bitwarden**](#install-bitwarden) on your machine.
|
||||
5. [**Configure your Environment**](#configure-your-environment) by adjusting settings in `./bwdata/env/global.override.env`.
|
||||
{% callout success %}At a minimum, configure the `globalSettings__mail__smtp...` variables to setup an email server for inviting and verifying users.{% endcallout %}
|
||||
@@ -140,24 +140,24 @@ Bitwarden provides a shell script for easy installation on Linux and macOS (Bash
|
||||
Typically, this value should be the configured DNS record.
|
||||
- **Do you want to use Let's Encrypt to generate a free SSL certificate? (y/n):**
|
||||
|
||||
Specify `y` to generate a trusted SSL certificate using Let's Encrypt. You will be prompted to enter an email address for expiration reminders from Let's Encrypt. For more information, see [Certificate Options]({% link _articles/hosting/certificates.md %}).
|
||||
Specify `y` to generate a trusted SSL certificate using Let's Encrypt. You will be prompted to enter an email address for expiration reminders from Let's Encrypt. For more information, see [Certificate Options]({{site.baseurl}}/article/certificates/).
|
||||
|
||||
Alternatively, specify `n` and use the **Do you have a SSL certificate to use?** option.
|
||||
|
||||
- **Enter your installation id:**
|
||||
|
||||
Retrieve an installation id using a valid email at [https://bitwarden.com/host](https://bitwarden.com/host). For more information, see [What are my installation id and installation key used for?](https://bitwarden.com/help/article/hosting-faqs/#general).
|
||||
Retrieve an installation id using a valid email at [https://bitwarden.com/host](https://bitwarden.com/host). For more information, see [What are my installation id and installation key used for?]({{site.baseurl}}/article/hosting-faqs/#general).
|
||||
- **Enter your installation key:**
|
||||
|
||||
Retrieve an installation key using a valid email at [https://bitwarden.com/host](https://bitwarden.com/host). For more information, see [What are my installation id and installation key used for?](https://bitwarden.com/help/article/hosting-faqs/#general).
|
||||
Retrieve an installation key using a valid email at [https://bitwarden.com/host](https://bitwarden.com/host). For more information, see [What are my installation id and installation key used for?]({{site.baseurl}}/article/hosting-faqs/#general).
|
||||
- **Do you have a SSL certificate to use? (y/n):**
|
||||
|
||||
If you already have your own SSL certificate, specify `y` and place the necessary files in the `.bwdata/ssl/your.domain` directory. You will be asked whether it is a trusted SSL certificate (y/n). For more information, see [Certificate Options]({% link _articles/hosting/certificates.md %}).
|
||||
If you already have your own SSL certificate, specify `y` and place the necessary files in the `.bwdata/ssl/your.domain` directory. You will be asked whether it is a trusted SSL certificate (y/n). For more information, see [Certificate Options]({{site.baseurl}}/article/certificates/).
|
||||
|
||||
Alternatively, specify `n` and use the **self-signed SSL certificate?** option, which is only recommended for testing purposes.
|
||||
- **Do you want to generate a self-signed SSL certificate? (y/n):**
|
||||
|
||||
Specify `y` to have Bitwarden generate a self-signed certificate for you. This option is only recommended for testing. For more information, see [Certificate Options]({% link _articles/hosting/certificates.md %}).
|
||||
Specify `y` to have Bitwarden generate a self-signed certificate for you. This option is only recommended for testing. For more information, see [Certificate Options]({{site.baseurl}}/article/certificates/).
|
||||
|
||||
If you specify `n`, your instance will not use an SSL certificate and you will be required to front your installation with a HTTPS proxy, or else Bitwarden applications will not function properly.
|
||||
|
||||
@@ -210,7 +210,7 @@ After editing `global.override.env`, run one of the following commands to apply
|
||||
|
||||
.\bitwarden.ps1 -restart
|
||||
|
||||
For more information about configuring Environment Variables, see [Configure Environment Variables]({% link _articles/hosting/environment-variables.md %}).
|
||||
For more information about configuring Environment Variables, see [Configure Environment Variables]({{site.baseurl}}/article/environment-variables/).
|
||||
|
||||
### Start Bitwarden
|
||||
|
||||
|
||||
@@ -5,13 +5,13 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, licensing]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
Self-hosting Bitwarden is free, however some features must be unlocked in your self-hosted instance with a registered license file. A license file can be obtained from the Bitwarden-hosted [Web Vault](https://vault.bitwarden.com){:target="\_blank"} by either an account with a Premium Individual subscription or by the Owner of an Organization.
|
||||
|
||||
{% callout info %}
|
||||
The procedures in this article assume that you have already started a paid subscription to Bitwarden. If you haven't, refer to [About Bitwarden Plans]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}) and [What Plan is Right for Me?]({% link _articles/plans-and-pricing/what-plan-is-right-for-me.md %}).
|
||||
The procedures in this article assume that you have already started a paid subscription to Bitwarden. If you haven't, refer to [About Bitwarden Plans]({{site.baseurl}}/article/about-bitwarden-plans/) and [What Plan is Right for Me?]({{site.baseurl}}/article/what-plan-is-right-for-me/).
|
||||
{% endcallout %}
|
||||
|
||||
## Individual License
|
||||
@@ -28,7 +28,7 @@ To retrieve your license from your Cloud account and apply it to your self-hoste
|
||||
|
||||
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.
|
||||
|
||||
{% callout success %}If you haven't already, verify your email address before proceeding. You will need to have [configured SMTP-related environment variables]({{site.baseurl}}/article/environment-variables) to do so.{% endcallout %}
|
||||
{% callout success %}If you haven't already, verify your email address before proceeding. You will need to have [configured SMTP-related environment variables]({{site.baseurl}}/article/environment-variables/) to do so.{% endcallout %}
|
||||
2. Select the **Settings** tab from the top navigation.
|
||||
3. Select **Go Premium** from the left menu.
|
||||
4. In the License File section, select the **Browse...** button and add the downloaded license file.
|
||||
@@ -39,7 +39,7 @@ To retrieve your license from your Cloud account and apply it to your self-hoste
|
||||
To retrieve your Organization license from your Cloud Organization and apply it to you self-hosted server:
|
||||
|
||||
{% callout info %}
|
||||
You must be an [Organization Owner]({{site.baseurl}}/article/user-types-access-control) to both retrieve and apply a license.
|
||||
You must be an [Organization Owner]({{site.baseurl}}/article/user-types-access-control/) to both retrieve and apply a license.
|
||||
{% endcallout %}
|
||||
|
||||
#### Retrieve your License
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, docker, install, deploy]
|
||||
order: 03
|
||||
order: "03"
|
||||
---
|
||||
|
||||
This article will walk you through procedures for transitioning from Cloud to Self-hosted, from Self-hosted to Cloud, and from one self-hosted server to another:
|
||||
@@ -29,22 +29,22 @@ This article will walk you through procedures for transitioning from Cloud to Se
|
||||
|
||||
To migrate from the Cloud to a self-hosted server:
|
||||
|
||||
1. [Install and deploy]({{site.baseurl}}/article/install-on-premise) Bitwarden to your server. At a high-level, this procedure involves:
|
||||
1. [Install and deploy]({{site.baseurl}}/article/install-on-premise/) Bitwarden to your server. At a high-level, this procedure involves:
|
||||
|
||||
1. [Configuring a domain]({{site.baseurl}}/article/install-on-premise/#configure-your-domain) for Bitwarden.
|
||||
2. Installing [Docker and Docker Compose]({{site.baseurl}}/article/install-on-premise/#install-docker-and-docker-compose).
|
||||
3. Running the [installation shell script]({{site.baseurl}}/article/install-on-premise/#install-bitwarden).
|
||||
4. [Configuring your environment]({{site.baseurl}}/article/install-on-premise/#configure-your-environment) to setup the Admin Portal, an SMTP Server connection, and more.
|
||||
2. Start your server by running `./bitwarden.sh start`.
|
||||
3. Open the Cloud Web Vault and [download your license]({{site.baseurl}}/article/licensing-on-premise).
|
||||
3. Open the Cloud Web Vault and [download your license]({{site.baseurl}}/article/licensing-on-premise/).
|
||||
|
||||
{% callout success %}There are separate files for an [Organization license]({{site.baseurl}}/article/licensing-on-premise/#organization-license) and an [Individual license]({{site.baseurl}}/article/licensing-on-premise/#individual-license). **You don't need both license files.** If you're migrating an Organization, you only need to retrieve the Organization license and must be an [Organization Owner]({{site.baseurl}}/article/user-types-access-control/) to do so.{% endcallout %}
|
||||
4. Still in the Cloud Web Vault, [export your personal Vault data]({{site.baseurl}}/article/export-your-data/#export-a-personal-vault) or [export your Organization Vault data]({{site.baseurl}}/article/export-your-data/#export-an-organization-vault). If you're migrating an Organization, encourage your end-users to export their Personal Vaults as well.
|
||||
5. Open your self-hosted Web Vault and create an account. This account **must use the same email address** as the Cloud account you downloaded the license with.
|
||||
5. Still in your self-hosted Web Vault, upload your [license]({{site.baseurl}}/article/licensing-on-premise).
|
||||
6. Still in your self-hosted Web Vault, upload your [license]({{site.baseurl}}/article/licensing-on-premise/).
|
||||
|
||||
{% callout success %}There are separate locations in which to upload an [Organization license]({{site.baseurl}}/article/licensing-on-premise/#organization-license) versus an [Individual license]({{site.baseurl}}/article/licensing-on-premise/#individual-license). As before, only upload the one that's relevant for you.{% endcallout %}
|
||||
6. Still in the self-hosted Web Vault, import data to your [Personal Vault]({{site.baseurl}}/article/import-your-data/) or [Organization Vault]({{site.baseurl}}/article/import-to-org/).
|
||||
7. Still in the self-hosted Web Vault, import data to your [Personal Vault]({{site.baseurl}}/article/import-data/) or [Organization Vault]({{site.baseurl}}/article/import-to-org/).
|
||||
|
||||
{% callout info %}Importing data to an Organization will automatically re-create your [Collections]({{site.baseurl}}/article/about-collections/) and add the relevant Vault items to them.{% endcallout %}
|
||||
|
||||
@@ -52,9 +52,9 @@ To migrate from the Cloud to a self-hosted server:
|
||||
|
||||
If you're migrating an Organization to a self-hosted server, continue with the following steps:
|
||||
|
||||
1. (**Enterprise Organizations Only**) Re-implement your [Enterprise Policy]({{site.baseurl}}/article/policies) specifications and/or configure [Login with SSO]({{site.baseurl}}/article/about-sso/).
|
||||
1. (**Enterprise Organizations Only**) Re-implement your [Enterprise Policy]({{site.baseurl}}/article/policies/) specifications and/or configure [Login with SSO]({{site.baseurl}}/article/about-sso/).
|
||||
2. Manually [re-create user Groups]({{site.baseurl}}/article/about-groups/#create-a-group) in your self-hosted Web Vault and assign them to the proper Collections.
|
||||
3. Start [inviting users to your Organization]({{site.baseurl}}/article/managing-users/#invite) manually or using [Directory Connector]({{site.baseurl}}/article/directory-sync).
|
||||
3. Start [inviting users to your Organization]({{site.baseurl}}/article/managing-users/#invite) manually or using [Directory Connector]({{site.baseurl}}/article/directory-sync/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
@@ -73,7 +73,7 @@ To migrate from a self-hosted server to the Cloud:
|
||||
3. Open the Cloud Web Vault. Most users will have previously created Cloud accounts for billing purposes, so log in to that account. If you were previously a free user without a Cloud account for billing, create an account now.
|
||||
|
||||
{% callout success %}If you're migrating an Organization, you'll already have a Cloud Organization established for billing and licensing purposes. For smoothest transition, we recommend using this already-established Organization rather than [creating a new one]({{site.baseurl}}/article/about-organizations/#create-an-organization).{% endcallout %}
|
||||
4. Still in the self-hosted Web Vault, import data to your [Personal Vault]({{site.baseurl}}/article/import-your-data/) or [Organization Vault]({{site.baseurl}}/article/import-to-org/).
|
||||
4. Still in the self-hosted Web Vault, import data to your [Personal Vault]({{site.baseurl}}/article/import-data/) or [Organization Vault]({{site.baseurl}}/article/import-to-org/).
|
||||
|
||||
{% callout info %}Importing data to an Organization will automatically re-create your [Collections]({{site.baseurl}}/article/about-collections/) and add the relevant Vault items to them.{% endcallout %}
|
||||
5. Manually upload [file attachments]({{site.baseurl}}/article/attachments/) to your Personal or Organization Vault.
|
||||
@@ -82,9 +82,9 @@ To migrate from a self-hosted server to the Cloud:
|
||||
|
||||
If you're migrating an Organization to the Cloud, continue with the following steps:
|
||||
|
||||
1. (**Enterprise Organizations Only**) Re-implement your [Enterprise Policy]({{site.baseurl}}/article/policies) specifications and/or configure [Login with SSO]({{site.baseurl}}/article/about-sso/).
|
||||
1. (**Enterprise Organizations Only**) Re-implement your [Enterprise Policy]({{site.baseurl}}/article/policies/) specifications and/or configure [Login with SSO]({{site.baseurl}}/article/about-sso/).
|
||||
2. Manually [re-create user Groups]({{site.baseurl}}/article/about-groups/#create-a-group) in the Cloud and assign them to the proper Collections.
|
||||
3. Start [inviting users to your Organization]({{site.baseurl}}/article/managing-users/#invite) manually or using [Directory Connector]({{site.baseurl}}/article/directory-sync).
|
||||
3. Start [inviting users to your Organization]({{site.baseurl}}/article/managing-users/#invite) manually or using [Directory Connector]({{site.baseurl}}/article/directory-sync/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [hosting]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [hosting, update]
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
{% callout success %}
|
||||
@@ -17,7 +17,7 @@ Please be aware that self-hosted server releases lag several days behind Cloud s
|
||||
Additionally, newer versions of client applications may not support older versions of your self-hosted instance.
|
||||
|
||||
{% callout warning %}
|
||||
We highly recommend backing up your data before updating your self-hosted instance. For more information, see [Backup your Hosted Data]({% link _articles/hosting/backup-on-premise.md %}).
|
||||
We highly recommend backing up your data before updating your self-hosted instance. For more information, see [Backup your Hosted Data]({{site.baseurl}}/article/backup-on-premise/).
|
||||
{% endcallout %}
|
||||
|
||||
Update your Bitwarden instance using the same Bash (Linux or macOS) or Powershell (Windows) script (`bitwarden.sh`) used to install Bitwarden. Run the following sequence of commands:
|
||||
|
||||
@@ -5,10 +5,10 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import]
|
||||
order: 09
|
||||
order: "09"
|
||||
---
|
||||
|
||||
This article defines the format you should use when manually conditioning a `.csv` or `.json` for import into Bitwarden. This format is identical to that used by `.csv` or `.json` files created by [Exporting your Bitwarden Vault]({% link _articles/account/export-your-data.md %}).
|
||||
This article defines the format you should use when manually conditioning a `.csv` or `.json` for import into Bitwarden. This format is identical to that used by `.csv` or `.json` files created by [Exporting your Bitwarden Vault]({{site.baseurl}}/article/export-your-data/).
|
||||
|
||||
Make sure that you're using the format for Personal Vaults or Organizations depending on your export/import operation, as they are slightly different.
|
||||
|
||||
|
||||
@@ -5,13 +5,13 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
Vault data can be [exported]({% link _articles/account/export-your-data.md %}) in an encrypted JSON file. These exports are encrypted using your [account's encryption key]({% link _articles/account/account-encryption-key.md %}), which are generated on account creation and unique to each Bitwarden user account.
|
||||
Vault data can be [exported]({{site.baseurl}}/article/export-your-data/) in an encrypted JSON file. These exports are encrypted using your [account's encryption key]({{site.baseurl}}/article/account-encryption-key/), which are generated on account creation and unique to each Bitwarden user account.
|
||||
|
||||
{% callout warning %}
|
||||
[Rotating your account's encryption key]({% link _articles/account/account-encryption-key.md %}) will render an Encrypted Export impossible to decrypt. **If you rotate your account encryption key, replace any old files with new one that use the new encryption key.**
|
||||
[Rotating your account's encryption key]({{site.baseurl}}/article/account-encryption-key/) will render an Encrypted Export impossible to decrypt. **If you rotate your account encryption key, replace any old files with new one that use the new encryption key.**
|
||||
|
||||
Account Encryption Keys are unique to each Bitwarden user account, so you won't be able to import an Encrypted Export into a different account.
|
||||
{% endcallout %}
|
||||
@@ -42,7 +42,7 @@ Will look something like:
|
||||
|
||||
## Create an Encrypted Export
|
||||
|
||||
Creating an Encrypted Export follows the [normal export procedure]({% link _articles/account/export-your-data.md %}):
|
||||
Creating an Encrypted Export follows the [normal export procedure]({{site.baseurl}}/article/export-your-data/):
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
@@ -132,7 +132,7 @@ To create an encrypted export of your personal Vault data from the CLI, use the
|
||||
bw export my-master-password --output /users/me/documents/ --format encrypted_json
|
||||
```
|
||||
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more detail, see our [CLI documentation]({{site.baseurl}}/article/cli/).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
@@ -141,13 +141,13 @@ For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli
|
||||
|
||||
## Import an Encrypted Export
|
||||
|
||||
Importing an Encrypted Export follows the [normal import procedure]({% link _articles/importing/import-data.md %}), which can **only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
Importing an Encrypted Export follows the [normal import procedure]({{site.baseurl}}/article/import-data/), which can **only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
|
||||
1. In the Web Vault, select **Tools** from the top navigation bar.
|
||||
2. Select **Import Data** from the left-hand Tools menu.
|
||||
3. From the format dropdown, choose **Bitwarden (json)**.
|
||||
|
||||
{% callout success %}There is no import option specifically for Encrypted Exports. A handler will determine that the `.json` file is encrypted and attempt to decrypt the file using your [account's encryption key]({% link _articles/account/account-encryption-key.md %}).{% endcallout %}
|
||||
{% callout success %}There is no import option specifically for Encrypted Exports. A handler will determine that the `.json` file is encrypted and attempt to decrypt the file using your [account's encryption key]({{site.baseurl}}/article/account-encryption-key/).{% endcallout %}
|
||||
5. Select the **Choose File** button and add the file to import.
|
||||
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
|
||||
@@ -5,18 +5,18 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: true
|
||||
tags: [import]
|
||||
order: 01
|
||||
order: "01"
|
||||
---
|
||||
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your personal Vault or Organization Vault. You can also use the data import tool to import from one Bitwarden Vault to another, or to import a Bitwarden [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your personal Vault or Organization Vault. You can also use the data import tool to import from one Bitwarden Vault to another, or to import a Bitwarden [Encrypted Export]({{site.baseurl}}/article/encrypted-export/).
|
||||
|
||||
For a full list of supported import formats, see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/import-faqs/#q-what-file-formats-does-bitwarden-support-for-import), or use one of these articles for importing from the most popular solutions:
|
||||
|
||||
- [Import from LastPass]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- [Import from 1Password]({% link _articles/importing/import-from-1password.md %})
|
||||
- [Import from Firefox]({% link _articles/importing/import-from-firefox.md %})
|
||||
- [Import from Google Chrome]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Import from Password Safe]({% link _articles/importing/import-from-passwordsafe.md %})
|
||||
- [Import from LastPass]({{site.baseurl}}/article/import-from-lastpass/)
|
||||
- [Import from 1Password]({{site.baseurl}}/article/import-from-1password/)
|
||||
- [Import from Firefox]({{site.baseurl}}/article/import-from-firefox/)
|
||||
- [Import from Google Chrome]({{site.baseurl}}/article/import-from-chrome/)
|
||||
- [Import from Password Safe]({{site.baseurl}}/article/import-from-passwordsafe/)
|
||||
|
||||
{% callout success %}
|
||||
**Not already signed up?** Choose from one of [Bitwarden's plans](https://bitwarden.com/pricing/business/){:target="\_blank"} and get started today:
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import, 1password]
|
||||
order: 03
|
||||
order: "03"
|
||||
---
|
||||
|
||||
Use this article for help exporting data from 1Passwords and importing into Bitwarden. 1Password data exports are available as `.1pif` or `.csv` files, depending on which client version and operating system you are using.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import, chrome, opera, vivaldi, edge]
|
||||
order: 04
|
||||
order: "04"
|
||||
---
|
||||
|
||||
Use this article for help exporting data from Google Chrome and importing into Bitwarden.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import, firefox]
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
Use this article for help exporting data from Firefox and importing into Bitwarden.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: true
|
||||
tags: [import, lastpass]
|
||||
order: 02
|
||||
order: "02"
|
||||
---
|
||||
|
||||
Use this article for help exporting data from LastPass and importing into Bitwarden.
|
||||
@@ -115,11 +115,11 @@ If you continue to have trouble locating the offending item using the data provi
|
||||
|
||||
### Maximum Collections Error
|
||||
|
||||
When importing Lastpass `.csv` exports to a [Free Organization]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}), you may observe the following error:
|
||||
When importing Lastpass `.csv` exports to a [Free Organization]({{site.baseurl}}/article/about-bitwarden-plans/), you may observe the following error:
|
||||
|
||||
{% image importing/lpcollectionserror.png Free Organization Max Collections Error%}
|
||||
|
||||
This error occurs when the Lastpass export contains 3 or more `grouping` values. The values in the `grouping` field are interpreted by Bitwarden as [Collections]({% link _articles/organizations/about-collections.md %}), however [Free Organizations]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}) are limited to only two Collections. The following `.csv`, for example, would cause this error:
|
||||
This error occurs when the Lastpass export contains 3 or more `grouping` values. The values in the `grouping` field are interpreted by Bitwarden as [Collections]({{site.baseurl}}/article/about-collections/), however [Free Organizations]({{site.baseurl}}/article/about-bitwarden-plans/) are limited to only two Collections. The following `.csv`, for example, would cause this error:
|
||||
|
||||
```
|
||||
url,username,password,totp,extra,name,grouping,fav
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [import-export]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [import, passwordsafe]
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
Use this article for help exporting data from Password Safe and importing into Bitwarden. Password Safe (V8) currently only supports exporting as `.csv` file. Older versions also supported `.xml`.
|
||||
@@ -35,7 +35,7 @@ Complete the following steps to export data from the Password Safe Desktop App:
|
||||
## Prepare exported file before import
|
||||
Currently we do not offer a specific importer for this type of file.
|
||||
|
||||
To prepare the exported file for import, please follow the instructions in this guide: [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %})
|
||||
To prepare the exported file for import, please follow the instructions in this guide: [Condition a Bitwarden .csv or .json]({{site.baseurl}}/article/condition-bitwarden-import/)
|
||||
|
||||
## Import to Bitwarden
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: true
|
||||
tags: [import, lastpass]
|
||||
order: 99
|
||||
order: "99"
|
||||
---
|
||||
## Bitwarden exclusive content: Making migration easy
|
||||
|
||||
@@ -44,8 +44,8 @@ Data imported into Bitwarden is defined as one of four item types:
|
||||
|
||||
Bitwarden currently limits the length of item fields to 1,000 characters, and Secure Notes to 10,000 characters. Items that exceed that criteria should be saved as separate files (text, key, pem, ssh, etc.) and added as attachments to an item.
|
||||
|
||||
- [More on Items](https://bitwarden.com/help/article/managing-items/)
|
||||
- [Attaching a file to an item](https://bitwarden.com/help/article/attachments/)
|
||||
- [More on Items]({{site.baseurl}}/article/managing-items/)
|
||||
- [Attaching a file to an item]({{site.baseurl}}/article/attachments/)
|
||||
|
||||
Gathering a full export of your data across your LastPass Organization may require assigning all shared folders to a single user, or performing multiple exports - one for each segment of shared folders.
|
||||
|
||||
@@ -55,9 +55,9 @@ Exported data from LastPass will contain data from both your Personal vault, as
|
||||
|
||||
Shared or company-level data is stored in a Bitwarden Organization. The best practice is to create this Organization first and import it directly, instead of importing the data into an individual account and then sharing it with the organization secondarily.
|
||||
|
||||
For more on creating a Bitwarden Organization, visit [this article.](https://bitwarden.com/help/article/about-organizations/)
|
||||
For more on creating a Bitwarden Organization, visit [this article.]({{site.baseurl}}/article/about-organizations/)
|
||||
|
||||
Self-hosted instances will need to create an Organization on the Bitwarden cloud instance to generate their [license key](https://bitwarden.com/host/) and can then proceed with [installing and configuring a Bitwarden Server instance.](https://bitwarden.com/help/article/install-on-premise/)
|
||||
Self-hosted instances will need to create an Organization on the Bitwarden cloud instance to generate their [license key](https://bitwarden.com/host/) and can then proceed with [installing and configuring a Bitwarden Server instance.]({{site.baseurl}}/article/install-on-premise/)
|
||||
|
||||
{%callout%}
|
||||
Self-hosting is available for Enterprise plans.
|
||||
@@ -67,15 +67,15 @@ Self-hosting is available for Enterprise plans.
|
||||
|
||||
Bitwarden Enterprise plans support Login with Single-Sign-On using either SAML 2.0 or OpenID Connect (OIDC).
|
||||
|
||||
Each Bitwarden Organization can configure one SSO provider. Configuration for this is located in the [Business Portal](https://bitwarden.com/help/article/about-business-portal/), accessible from the Web Vault by Organization Owners and Administrators.
|
||||
Each Bitwarden Organization can configure one SSO provider. Configuration for this is located in the [Business Portal]({{site.baseurl}}/article/about-business-portal/), accessible from the Web Vault by Organization Owners and Administrators.
|
||||
|
||||
For more details on Login with SSO configurations and examples of Identity Provider (IdP) settings and naming conventions, please visit [these help articles](https://bitwarden.com/help/article/about-sso/).
|
||||
For more details on Login with SSO configurations and examples of Identity Provider (IdP) settings and naming conventions, please visit [these help articles]({{site.baseurl}}/article/about-sso/).
|
||||
|
||||
### Enabling enterprise policies
|
||||
|
||||
Policies are found in the [Business Portal](https://bitwarden.com/help/article/about-business-portal/)
|
||||
Policies are found in the [Business Portal]({{site.baseurl}}/article/about-business-portal/)
|
||||
|
||||
Policies allow you to control the actions of users within your Organization. It is recommended to configure these policies prior to onboarding users. For a complete list and details for Enterprise Policies, please see our helpful article [here.](https://bitwarden.com/help/article/policies/)
|
||||
Policies allow you to control the actions of users within your Organization. It is recommended to configure these policies prior to onboarding users. For a complete list and details for Enterprise Policies, please see our helpful article [here.]({{site.baseurl}}/article/policies/)
|
||||
|
||||
## Importing data
|
||||
|
||||
@@ -88,9 +88,9 @@ Creating a Bitwarden specific CSV from your exported data
|
||||
|
||||
The best practice for most Organizations is to format your data into a Bitwarden CSV, or for advanced users, a Bitwarden JSON file for import into your Organization vault.
|
||||
|
||||
For instructions on shaping a Bitwarden specific import file, please refer to the guide [here.](https://bitwarden.com/help/article/condition-bitwarden-import/)
|
||||
For instructions on shaping a Bitwarden specific import file, please refer to the guide [here.]({{site.baseurl}}/article/condition-bitwarden-import/)
|
||||
|
||||
A collection of data import and export documentation is available [here.](https://bitwarden.com/help/import-export/) to assist with imports from additional sources.
|
||||
A collection of data import and export documentation is available [here.]({{site.baseurl}}/article/import-export/) to assist with imports from additional sources.
|
||||
|
||||
{%callout%}
|
||||
Importing multiple times will create duplicate records in your Bitwarden Vault.
|
||||
@@ -100,7 +100,7 @@ Importing multiple times will create duplicate records in your Bitwarden Vault.
|
||||
|
||||
Bitwarden supports a variety import formats from other password management platforms. Individual users can import their data into their Bitwarden Vault on their own, and does not require Administrative assistance.
|
||||
|
||||
For more on importing individual data, check out our helpful article [here.](https://bitwarden.com/help/import-export/)
|
||||
For more on importing individual data, check out our helpful article [here.]({{site.baseurl}}/article/import-export/)
|
||||
|
||||
## Onboarding users
|
||||
|
||||
@@ -108,15 +108,15 @@ Bitwarden supports both manual and automated user invitation and boarding. Best
|
||||
|
||||
### Manual onboarding
|
||||
|
||||
Manual boarding is done via the Web Vault. More information on manual user boarding can be found in this [helpful article](https://bitwarden.com/help/article/managing-users/)
|
||||
Manual boarding is done via the Web Vault. More information on manual user boarding can be found in this [helpful article]({{site.baseurl}}/article/managing-users/)
|
||||
|
||||
### Automated onboarding
|
||||
|
||||
Automated user boarding is also available when leveraging Bitwarden Directory Connector - a standalone application available in a [Desktop app](https://bitwarden.com/help/article/directory-sync-desktop/) and a [CLI tool](https://bitwarden.com/help/article/directory-sync-cli/) - synchronizing user and group information to the Bitwarden Organization. These users are automatically invited to join the Organization, and can be confirmed manually or automatically using the [Bitwarden CLI tool](https://bitwarden.com/help/article/cli/#confirm).
|
||||
Automated user boarding is also available when leveraging Bitwarden Directory Connector - a standalone application available in a [Desktop app]({{site.baseurl}}/article/directory-sync-desktop/) and a [CLI tool]({{site.baseurl}}/article/directory-sync-cli/) - synchronizing user and group information to the Bitwarden Organization. These users are automatically invited to join the Organization, and can be confirmed manually or automatically using the [Bitwarden CLI tool]({{site.baseurl}}/article/cli/#confirm).
|
||||
|
||||
- Learn more about how syncing works [here.](https://bitwarden.com/help/article/directory-sync/)
|
||||
- Discover how to configure user and group filters for Directory Connector [here.](https://bitwarden.com/help/article/user-group-filters/)
|
||||
- Documentation for multiple Directory Connector options is available [here.](https://bitwarden.com/help/directory-connector/)
|
||||
- Learn more about how syncing works [here.]({{site.baseurl}}/article/directory-sync/)
|
||||
- Discover how to configure user and group filters for Directory Connector [here.]({{site.baseurl}}/article/user-group-filters/)
|
||||
- Documentation for multiple Directory Connector options is available [here.]({{site.baseurl}}/article/directory-connector/)
|
||||
|
||||
## Sharing Collections and items
|
||||
|
||||
@@ -126,7 +126,7 @@ Bitwarden empowers Teams and Organizations to share sensitive data easily, secur
|
||||
|
||||
Collections organize secure items in many ways, including but not limited to: business function, group assignment, application access levels, or even security protocols. Collections perform the same functions as shared folders, allowing for consistent access control and sharing amongst groups of users.
|
||||
|
||||
Shared folders from LastPass can be imported as Collections into Bitwarden by using the Organization Import template found [here](https://bitwarden.com/help/files/bitwarden_export_org.csv) and placing the name of the shared folder in the Collection column.
|
||||
Shared folders from LastPass can be imported as Collections into Bitwarden by using the Organization Import template found [here]({{site.baseurl}}/article/files/bitwarden_export_org.csv) and placing the name of the shared folder in the Collection column.
|
||||
|
||||
Example LastPass Export:
|
||||
|
||||
@@ -138,7 +138,7 @@ Example Bitwarden Organization Import
|
||||
|
||||
Collections can be shared with both Groups and Individual users. Limiting the number of individual users that can access a Collection will make management more efficient for Administrators.
|
||||
|
||||
For more information on assigning Collections to Users and Groups, please refer to our help article [here.](https://bitwarden.com/help/article/about-collections/)
|
||||
For more information on assigning Collections to Users and Groups, please refer to our help article [here.]({{site.baseurl}}/article/about-collections/)
|
||||
|
||||
### Groups
|
||||
|
||||
@@ -146,7 +146,7 @@ Leveraging Groups for sharing is the most effective way to provide credential an
|
||||
|
||||
As a part of deployment preparations, it is possible to synchronize **just** groups from the LDAP directory before synchronization of Users begins, such that Collections can be assigned to Groups before users begin accessing Bitwarden.
|
||||
|
||||
For more information on filtering and synchronization of Users with the Bitwarden Directory Connector, please check out the article [here.](https://bitwarden.com/help/article/user-group-filters/)
|
||||
For more information on filtering and synchronization of Users with the Bitwarden Directory Connector, please check out the article [here.]({{site.baseurl}}/article/user-group-filters/)
|
||||
|
||||
### Permissions
|
||||
|
||||
@@ -165,7 +165,7 @@ Bitwarden uses an union of permissions to determine final access permissions for
|
||||
- User A is also a member of the Support Management group, which has access to the Support Collection, with read-write access.
|
||||
- In this scenario, User A will be able to read-write to the Collection.
|
||||
|
||||
More information on permissions can be found on our help site [here.](https://bitwarden.com/help/article/user-types-access-control/#access-control)
|
||||
More information on permissions can be found on our help site [here.]({{site.baseurl}}/article/user-types-access-control/#access-control)
|
||||
|
||||
## Migration support
|
||||
|
||||
@@ -175,7 +175,7 @@ The Bitwarden Customer Success team is available 24/7 with priority support for
|
||||
|
||||
### Organization
|
||||
|
||||
- A Bitwarden Organization is the encompassing “object” that relates all data for a given sharing entity. Click [here](https://bitwarden.com/help/article/about-organizations/) for more information on Organizations.
|
||||
- A Bitwarden Organization is the encompassing “object” that relates all data for a given sharing entity. Click [here]({{site.baseurl}}/article/about-organizations/) for more information on Organizations.
|
||||
|
||||
### Folders for Individual Vaults
|
||||
|
||||
@@ -193,7 +193,7 @@ The Bitwarden Customer Success team is available 24/7 with priority support for
|
||||
|
||||
### Group
|
||||
|
||||
- Bitwarden and LastPass support User Groups. When migrating to Bitwarden, you can leverage [BWDC](https://bitwarden.com/help/directory-connector/) to synchronize your LDAP groups into your Bitwarden Organization.
|
||||
- Bitwarden and LastPass support User Groups. When migrating to Bitwarden, you can leverage [BWDC]({{site.baseurl}}/article/directory-connector/) to synchronize your LDAP groups into your Bitwarden Organization.
|
||||
|
||||
### Read Only
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [import, teams, enterprise, onboarding, security]
|
||||
order: 04
|
||||
order: "04"
|
||||
---
|
||||
|
||||
Secure migration of your Organization with Bitwarden is straightforward and secure. Simply follow the steps in this guide to migrate data and users from your existing password manager:
|
||||
@@ -33,7 +33,7 @@ Steps in this document **are listed in the recommended order** for ease of use a
|
||||
|
||||
Exporting data from another password manager will be different for each solution, and in some cases may be a bit tricky. Use one of our [Import & Export Guides]({{site.baseurl}}/import-export/) for help, for example with exporting from [Lastpass]({{site.baseurl}}/article/import-from-lastpass/#export-from-lastpass) or [1Password]({{site.baseurl}}/article/import-from-1password/#export-from-1password).
|
||||
|
||||
Gathering a full export of your data may require assigning shared folders or items to a single user for export, or performing multiple exports between users with appropriate permissions. Additionally, exported data may include personal data alongside shared/organizational data, so be sure to remove personal items from the export file before [importing to Bitwarden](#).
|
||||
Gathering a full export of your data may require assigning shared folders or items to a single user for export, or performing multiple exports between users with appropriate permissions. Additionally, exported data may include personal data alongside shared/organizational data, so be sure to remove personal items from the export file before [importing to Bitwarden](#step-3-import-data-to-your-organization).
|
||||
|
||||
{% callout info %}
|
||||
We recommend paying special attention to the location of the following types of data during export:
|
||||
@@ -57,12 +57,12 @@ It's important that you create your Organization first and [import data to it di
|
||||
|
||||
1. **Create your Organization**. Start by creating your Organization. To learn how, check out [this article]({{site.baseurl}}/article/about-organizations/#create-an-organization).
|
||||
|
||||
{% callout note %}To self-host Bitwarden, create an Organization on the Bitwarden cloud, generate a [license key](https://bitwarden.com/host/), and use the key to [unlock Organizations]({{site.baseurl}}/article/licensing-on-premise/#organization-license) on your server.{% endcallout %}
|
||||
{% callout info %}To self-host Bitwarden, create an Organization on the Bitwarden cloud, generate a [license key](https://bitwarden.com/host/), and use the key to [unlock Organizations]({{site.baseurl}}/article/licensing-on-premise/#organization-license) on your server.{% endcallout %}
|
||||
|
||||
2. **Onboard Administrative Users**. With your Organization created, further setup procedures can be made easier by onboarding some [administrative users]({{siter.baseurl}}/article/user-types-access-control). It's important that you **do not begin end-user onboarding** at this point, as there are a few steps left to prepare your Organization. Learn how to invite admins [here]({{site.baseurl}}/article/managing-users/#onboard-users).
|
||||
3. **Configure Identity Services**. Bitwarden Enterprise Organizations support [Login with Single-Sign-On]({{site.baseurl}}/article/about-sso/) using either SAML 2.0 or OpenID Connect (OIDC). To configure SSO, navigate to the [Business Portal](https://bitwarden.com/help/article/about-business-portal/), accessible from the Web Vault by [Organization Owners and Administrators]({{site.baseurl}}/article/user-types-access-control/).
|
||||
2. **Onboard Administrative Users**. With your Organization created, further setup procedures can be made easier by onboarding some [administrative users]({{siter.baseurl}}/article/user-types-access-control/). It's important that you **do not begin end-user onboarding** at this point, as there are a few steps left to prepare your Organization. Learn how to invite admins [here]({{site.baseurl}}/article/managing-users/#onboard-users).
|
||||
3. **Configure Identity Services**. Bitwarden Enterprise Organizations support [Login with Single-Sign-On]({{site.baseurl}}/article/about-sso/) using either SAML 2.0 or OpenID Connect (OIDC). To configure SSO, navigate to the [Business Portal]({{site.baseurl}}/article/about-business-portal/), accessible from the Web Vault by [Organization Owners and Administrators]({{site.baseurl}}/article/user-types-access-control/).
|
||||
|
||||
4. **Enable Enterprise Policies**. [Enterprise Policies]({{site.baseurl}}/article/) enable Enterprise Organizations to implement roles for users, for example requiring use of Two-step Login. It is highly recommended that you configure Policies before onboarding users.
|
||||
4. **Enable Enterprise Policies**. [Enterprise Policies]({{site.baseurl}}/article/policies/) enable Enterprise Organizations to implement roles for users, for example requiring use of Two-step Login. It is highly recommended that you configure Policies before onboarding users.
|
||||
|
||||
## Step 3: Import Data to your Organization
|
||||
|
||||
@@ -78,10 +78,10 @@ To import data to your Organization:
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
5. Select the **Import Data** button to complete your import.
|
||||
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({% link _articles/features/attachments.md %}).
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({{site.baseurl}}/article/attachments/).
|
||||
|
||||
{% callout success %}
|
||||
You should also recommend to employees that they export their personal data from your existing password manager and prepare it for import into Bitwarden. Learn more [here]({{site.baseurl}}/import-export/).
|
||||
You should also recommend to employees that they export their personal data from your existing password manager and prepare it for import into Bitwarden. Learn more [here]({{site.baseurl}}/article/import-data/).
|
||||
{% endcallout %}
|
||||
|
||||
### Import Recommendations
|
||||
@@ -103,9 +103,9 @@ To ensure the security of your Organization, Bitwarden applies a 3-step process
|
||||
|
||||
### Automated Onboarding
|
||||
|
||||
Automated user onboarding is available through [Bitwarden Directory Connector]({{site.baseurl}}/article/directory-sync), a standalone application available in a [Desktop app]({{site.baseurl}}/article/directory-sync-desktop/) and [CLI]({{site.baseurl}}/article/directory-sync-cli/) that will synchronize users and groups from your existing directory service.
|
||||
Automated user onboarding is available through [Bitwarden Directory Connector]({{site.baseurl}}/article/directory-sync/), a standalone application available in a [Desktop app]({{site.baseurl}}/article/directory-sync-desktop/) and [CLI]({{site.baseurl}}/article/directory-sync-cli/) that will synchronize users and groups from your existing directory service.
|
||||
|
||||
Users are automatically invited to join the Organization, and can be confirmed manually or automatically using the [Bitwarden CLI tool](https://bitwarden.com/help/article/cli/#confirm).
|
||||
Users are automatically invited to join the Organization, and can be confirmed manually or automatically using the [Bitwarden CLI tool]({{site.baseurl}}/article/cli/#confirm).
|
||||
|
||||
- Learn more about how syncing works [here]({{site.baseurl}}/article/directory-sync/).
|
||||
- Discover how to configure user and group filters for Directory Connector [here]({{site.baseurl}}/article/user-group-filters/).
|
||||
@@ -121,7 +121,7 @@ Bitwarden empowers Teams and Organizations to share sensitive data easily, secur
|
||||
|
||||
Collections can organize secure items in many ways, including but not limited to business function, group assignment, application access levels, or even security protocols. Collections function as shared folders, allowing for consistent access control and sharing amongst groups of users.
|
||||
|
||||
Shared folders from other password managers can be imported as Collections into Bitwarden by using the Organization Import template found [here](https://bitwarden.com/help/files/bitwarden_export_org.csv) and placing the name of the shared folder in the `Collection` column:
|
||||
Shared folders from other password managers can be imported as Collections into Bitwarden by using the Organization Import template found [here]({{site.baseurl}}/files/bitwarden_export_org.csv) and placing the name of the shared folder in the `Collection` column:
|
||||
|
||||
Example Export:
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [login-with-sso]
|
||||
featured: true
|
||||
popular: true
|
||||
tags: [saml, saml2.0, single sign-on, sso, oidc, openid, openid connect, idp, identity provider]
|
||||
order: 01
|
||||
order: "01"
|
||||
redirect_from:
|
||||
- /article/getting-started-with-sso/
|
||||
---
|
||||
@@ -18,21 +18,21 @@ Login with SSO currently supports SAML 2.0 and OpenID Connect authentication for
|
||||
|
||||
Users of Bitwarden authenticate into their vaults using the **Enterprise Single Sign-On** button located on the login screen of any Bitwarden client application. For more information, see [Using Login with SSO]({{site.baseurl}}/article/using-sso/).
|
||||
|
||||
Administrators can configure Login with SSO in the Business Portal. For more information, see [About the Business Portal](https://bitwarden.com/help/article/about-business-portal/).
|
||||
Administrators can configure Login with SSO in the Business Portal. For more information, see [About the Business Portal]({{site.baseurl}}/article/about-business-portal/).
|
||||
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
### Requiring SSO for Users
|
||||
|
||||
Using the **Single Sign-On Authentication** policy, Enterprise Organizations can require non-Owner/non-Admin users to log in to Bitwarden with Enterprise Single Sign-On. For more information about setting up this policy, see [Policies]({% link _articles/organizations/policies.md %}).
|
||||
Using the **Single Sign-On Authentication** policy, Enterprise Organizations can require non-Owner/non-Admin users to log in to Bitwarden with Enterprise Single Sign-On. For more information about setting up this policy, see [Policies]({{site.baseurl}}/article/policies/).
|
||||
|
||||
## Enterprise Free Trial
|
||||
|
||||
Login with SSO is available for all customers on the current Enterprise plan (for more information, see [About Bitwarden Plans]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}). If you're new to Bitwarden, we'd love to help you through the process of setting up an account and starting your 7 Day Free Trial Enterprise Organization with our dedicated signup page:
|
||||
Login with SSO is available for all customers on the current Enterprise plan (for more information, see [About Bitwarden Plans]({{site.baseurl}}/article/about-bitwarden-plans/). If you're new to Bitwarden, we'd love to help you through the process of setting up an account and starting your 7 Day Free Trial Enterprise Organization with our dedicated signup page:
|
||||
|
||||
<a role="button" class="btn btn-primary" href="https://vault.bitwarden.com/#/register?org=enterprise">Start your Enterprise Free Trial</a>
|
||||
|
||||
If you're an experienced Bitwarden user, refer to the [this article]({% link _articles/plans-and-pricing/enterprise-free-trial.md %}) for help. If you're self-hosting Bitwarden, you will need to generate a new license file after starting your 7 Day Free Trial. We recommend using a separate Bitwarden instance for testing Login with SSO. For more information, see [Licensing Paid Features](https://bitwarden.com/help/article/licensing-on-premise).
|
||||
If you're an experienced Bitwarden user, refer to the [this article]({{site.baseurl}}/article/enterprise-free-trial/) for help. If you're self-hosting Bitwarden, you will need to generate a new license file after starting your 7 Day Free Trial. We recommend using a separate Bitwarden instance for testing Login with SSO. For more information, see [Licensing Paid Features]({{site.baseurl}}/article/licensing-on-premise/).
|
||||
|
||||
## Requirements
|
||||
|
||||
@@ -54,7 +54,7 @@ Your Bitwarden client applications require the following versions:
|
||||
### Self-Hosting Requirements
|
||||
If you are self-hosting Bitwarden, your installation must be on v1.37+.
|
||||
|
||||
For information on updating your self-hosted instance, see [Updating your Self-Hosted Installation](https://bitwarden.com/help/article/updating-on-premise/).
|
||||
For information on updating your self-hosted instance, see [Updating your Self-Hosted Installation]({{site.baseurl}}/article/updating-on-premise/).
|
||||
|
||||
## Workflow Diagram
|
||||
The following diagram is an overview of the workflow used by Bitwarden to authenticate using SSO:
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [login-with-sso]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [sso, oidc, openid, idp, identity]
|
||||
order: 03
|
||||
order: "04"
|
||||
---
|
||||
|
||||
## Step 1: Set an Organization Identifier
|
||||
@@ -47,7 +47,7 @@ From this point on, **implementation will vary provider-to-provider**. Jump to o
|
||||
|
||||
### Configuration Reference Materials
|
||||
|
||||
The following sections will define fields configured in the [Bitwarden Business Portal]({{site.baseurl}}/article/about-business-portal), agnostic of which IdP you're integrating with. Fields that must be configured will be marked (**Required**).
|
||||
The following sections will define fields configured in the [Bitwarden Business Portal]({{site.baseurl}}/article/about-business-portal/), agnostic of which IdP you're integrating with. Fields that must be configured will be marked (**Required**).
|
||||
|
||||
{% callout success %}
|
||||
**Unless you're comfortable with OpenID Connect**, we recommend using one of the [above Implementation Guides](#step-3-configuration) instead of the following generic material.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [login-with-sso]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [sso, saml, saml2.0, idp, identity]
|
||||
order: 02
|
||||
order: "03"
|
||||
---
|
||||
|
||||
## Step 1: Set an Organization Identifier
|
||||
@@ -33,7 +33,7 @@ Once you have your Organization Identifier, you can proceed to enabling and conf
|
||||
|
||||
{% image sso/sso-bp-1.png Business Portal Menu %}
|
||||
3. Check the **Enabled** checkbox.
|
||||
4. From the **Type** dropdown menu, select the **SAML 2.0** option. If you intend to use OIDC instead, switch over to the [OIDC Configuration Guide]({{site.baseurl}}/article/configure-sso-oidc).
|
||||
4. From the **Type** dropdown menu, select the **SAML 2.0** option. If you intend to use OIDC instead, switch over to the [OIDC Configuration Guide]({{site.baseurl}}/article/configure-sso-oidc/).
|
||||
|
||||
## Step 3: Configuration
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Configuration involves working simultaneously within the Bitwarden [Business Por
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-adfs-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-adfs-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
@@ -15,12 +15,12 @@ Configuration involves working simultaneously within the Bitwarden [Business Por
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-auth0-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-auth0-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
|
||||
@@ -16,12 +16,12 @@ Configuration involves working simultaneously within the Bitwarden [Business Por
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-aws-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-aws-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
[Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
@@ -11,17 +11,17 @@ order:
|
||||
|
||||
This article contains **Azure-specific** help for configuring Login with SSO via SAML 2.0. For help configuring Login with SSO for another IdP, refer to [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/).
|
||||
|
||||
Configuration involves working simultaneously with the Bitwarden [Business Portal]({{site.baseurl}}/article/about-business-portal) and the Azure Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
Configuration involves working simultaneously with the Bitwarden [Business Portal]({{site.baseurl}}/article/about-business-portal/) and the Azure Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-azure-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-azure-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
[Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
@@ -15,7 +15,7 @@ Configuration involves working simultaneously between the Bitwarden [Business Po
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-duo-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-duo-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
@@ -24,7 +24,7 @@ Configuration involves working simultaneously between the Bitwarden [Business Po
|
||||
This article assumes that you have already set up Duo with an Identity Provider. If you haven't, see [Duo's documentation](https://duo.com/docs/sso#saml){:target="\_blank"} for details.
|
||||
{% endcallout %}
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
|
||||
@@ -16,12 +16,12 @@ Configuration involves working simultaneously with the Bitwarden [Business Porta
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-google-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-google-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
|
||||
@@ -16,12 +16,12 @@ Configuration involves working simultaneously within the Bitwarden [Business Por
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-jumpcloud-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-jumpcloud-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/sso-configure-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your [Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
|
||||
@@ -10,17 +10,17 @@ order:
|
||||
---
|
||||
This article contains **Keycloak-specific** help for configuring Login with SSO via SAML 2.0. For help configuring Login with SSO for another IdP, refer to [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/).
|
||||
|
||||
Configuration involves working simultaneously with the Bitwarden [Business Portal]({{site.baseurl}}/article/about-business-portal) and the Keycloak Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
Configuration involves working simultaneously with the Bitwarden [Business Portal]({{site.baseurl}}/article/about-business-portal/) and the Keycloak Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
|
||||
{% callout success %}
|
||||
**Already an SSO expert?** Skip the instructions in this article and download screenshots of sample configurations to compare against your own.
|
||||
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/files/saml-keycloak-sample.zip)
|
||||
[{% icon fa-download %} Download Sample]({{site.baseurl}}/article/files/saml-keycloak-sample.zip)
|
||||
{% endcallout %}
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created](https://bitwarden.com/help/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
If you're coming straight from [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/), you should already have an [Organization ID created]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and the SSO Configuration screen open. If you don't, open your
|
||||
[Business Portal]({{site.baseurl}}/article/about-business-portal/) and navigate to the SSO Configuration screen:
|
||||
|
||||
{% image sso/sso-saml1.png SAML 2.0 Configuration %}
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user