mirror of
https://github.com/bitwarden/help
synced 2026-01-06 02:23:22 +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:
fred_the_tech_writer
committed by
GitHub
GitHub
parent
63f78e8979
commit
906e2ca0dd
@@ -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.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user