ProductsDownloadPricingHelpBlogContact
Get Started
Log In
HomeProductsDownloadPricingHelpBlogContactTalk to SalesGet StartedLog In

Using URIs

Any login item in your vault can have one or more URIs (Uniform Resource Identifiers). A URI can be a website address (i.e. a URL), a Server IP Address, a Mobile App Package ID, and more.

Login item URI fields in the Web Vault
Login item URI fields in the Web Vault
note

Assigning URIs to login items is required if you want to use auto-fill in various Bitwarden apps.

URI Schemes

Well-formed URIs should include a scheme at the beginning, for example the https:// scheme to securely reference a website address. If no scheme is specified, http:// is assumed.

tip

Most Bitwarden apps allow you to Launch an website or app directly from your vault. Without a scheme, launching won't work properly.

Schemes include:

  • http:// or https:// reference website addresses (e.g. https://github.com)

  • androidapp:// references an Android Application Package ID or Name (e.g. androidapp://com.twitter.android)

tip

An easy way to obtain the proper URI for an Android app is to visit the app's page in the Google Play Store, tap the share button, and paste the copied link somewhere you can read it. The link will look like https://play.google.com/store/apps/details?id=com.twitter.android. The value after id= is your URI, in this case com.twitter.android. Learn more.

Match Detection Options

Each URI assigned to a login has an associated Match Detection option. This option determines when Bitwarden will offer the login as an available option for auto-fill, typically determined by matching against specific component pieces. The following graphic breaks down component pieces of a URI:

Diagram of a URI
Diagram of a URI

Default match detection

Bitwarden browser extensions and mobile apps allow you toselect a Default match detection behavior from the options listed next by navigating to SettingsOptionsDefault URI Match Detection. You can set match detection on an item-by-item basis, which will override the global default.

By default, Base domain matching is the default option.

Base domain

Selecting Base domain will prompt Bitwarden to offer auto-fill when the top-level domain and second-level domain of the URI match the detected resource.

For example, if the URI https://google.com uses base domain match detection:

Host

Selecting Host will prompt Bitwarden to offer auto-fill when the hostname and (if specified) port of the URI matches the detected resource.

For example, if the URI https://sub.domain.com:4000 uses host match detection:

Starts with

Selecting Starts with will prompt Bitwarden to offer auto-fill when the detected resource starts with the URI, regardless of what follows it.

For example, if the URI https://sub.domain.com/path/ uses starts with match detection:

Regular expression

warning

Regular expressions are an advanced option and can be quite dangerous if used incorrectly. You should not use this option if you do not know exactly what you're doing.

Selecting Regular expression will prompt Bitwarden to offer auto-fill when the detected resource matches a specified regular expression. Regular expressions are always case insensitive.

Unsafe example

If the URI ^https://.*google\.com$ uses regular expression match detection:

This probably matches more than what is intended. Consider avoiding periods (.), which unless escaped (\) match on any character.

Safe example

If the URI ^https://[a-z]+\.wikipedia\.org/w/index\.php uses regular expression match detection:

Exact

Selecting Exact will prompt Bitwarden to offer auto-fill when the URI matches the detected resource exactly.

For example, if the URI https://www.google.com/page.html uses exact match detection:

Never

Selecting Never will prompt Bitwarden to never offer auto-fill for the item.


Products

Resources

  • Resource Center
  • Community Forums
  • Security Compliance
  • Success Stories
  • User Reviews
  • Newsfeed
  • Subscribe to Updates

©2022 Bitwarden, Inc.

Terms Privacy Sitemap