* initial draft * codeblock e.g.'s * initial draft of f4e end-user doc * first round of feedback * feedback round 2 * feedback round 3 * update screenshots * safari/macos import guide sketch * adios, friendly name * cli note * fix typo * finish import from macos/safari * feedback round 4 * more feedback * updated diagrams * fix typo * linked custom fields & more release note items * new auto-fill unlock behavior for context menu & keyboard! * release notes - autofill unlock * new events * fixes to 'using sso' * updated KC screenshot & test step * KC URL * send extension & release notes * hide ios extension * updates to sso faqs * SEO desc's & tags * Key Connector > Impact on Unlock > Add a note for online dependency * clarify "account is lost" * add some references to CME * final edits * f4e * quick edit to RN
5.0 KiB
layout, title, categories, featured, popular, tags, order, description
| layout | title | categories | featured | popular | tags | order | description | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| article | Custom Fields |
|
false | false |
|
08 | Custom fields in the Bitwarden password manager enable you to add unique data to a login for autofill. Learn how to create one with just a few clicks. |
Custom fields, available for any Vault item type, 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).
- Boolean: Field value stores a boolean value (true/false).
- Linked: Field value is linked to the item's Username or Password. Given the right field name, Linked custom fields can be used to solve issues where your Browser Extension can't auto-fill usernames and passwords for a particular site (learn more).
{% 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.
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 %}
Creating Custom Fields
Custom fields can be added to a Vault item from any Bitwarden client using the Custom Fields section of the Edit Item panel:
{% image features/custom-fields.png Custom Fields in Web Vault %}
Custom Field Names
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):
{% image features/custom-fields-contextmenu.png %}
Selecting this context menu option will copy the form element's id, name, aria-label, or placeholder value (in that order of preference).
Once you've saved a custom field, you can auto-fill it from the Browser Extension.
Find Custom Field Names Manually
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:
{% image features/custom-fields/custom_field.gif Browser Extension Context Menu %}
-
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.
-
Find and copy the element
id(findid="xxx", wherexxxis the element'sidvalue). -
In the relevant Vault item's Custom Fields section, choose the appropriate field type and select the {% icon fa-plus %} New Custom Field button:
{% image features/custom-fields/types.png Select custom field type%}
-
Paste the copied element
idin the Name field. -
Specify the desired information to be auto-filled (in the above example, a PIN) in the Value field.
{% image features/custom-fields/custom-field-eg.png Custom field example %}
-
Save the Vault item.
Once you've saved a custom field, you can auto-fill it from the Browser Extension.
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:
- HTML form element's
idattribute. - HTML form element's
nameattribute. - HTML form element's
aria-labelattribute. - HTML form element's
placeholderattribute.
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
pin2ormypin
Prefixing
There are two cases in which you can exercise more control over 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 examplecsv=pin,mypin,pincode. - regex: Prefixing your custom field's name with
regex=allows you to perform regular expression comparisons{:target="_blank"} when auto-fill is performed. For example,regex=^first.*namewill offer auto-fill forfirstName,First_name, andFirst Name.