Using URIs

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.

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.

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)

Match Detection Options

Each URI assigned to a Login item has an associated Match Detection option. This option determines when and whether PassageWay 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:

Default match detection

Bitwarden Browser Extensions and Mobile Apps can select a Default match detection behavior from the options listed below by navigating to Settings → Options → Default URI Match Detection. You can also set match detection behavior on an item-by-item basis, which will override the global default.

By default, PassageWay will use Base domain matching as the default option.

Base domain

Selecting Base domain will prompt PassageWay to offer auto-fill when the top-level domain and second-level domain of a Login’s URI value match the detected resource.

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

Host

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

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

Starts with

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

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

Regular expression

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

Unsafe example

If the URI value ^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 value ^https://[a-z]+\.wikipedia\.org/w/index\.php uses regular expression match detection:

Exact

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

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

Never

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