Qualibrate Chrome Extension: Integrity Control and Permissions Mapping

<all_urls>

Matches any URL that uses a permitted scheme.

Allows the extension to interact (record/execute) with any webpage (depends on the URL of the Application under test)

webRequest

Gives your extension access to the chrome.webRequest API.

Tracks and gains the details of the loading state of the current website so that we can know when we can initiate actions.

https://*/*

Gives your extension access to run on all 'https' sites.

Similar to <all_urls>, but related to https pages

http://*/*

Gives your extension access to run on all 'http' sites.

Similar to <all_urls>, but related to http pages

tabs

Gives your extension access to privileged fields of the Tab objects used by several APIs including chrome.tabs and chrome.windows. In many circumstances your extension will not need to declare the "tabs" permission to make use of these APIs.

We need to keep track of active tabs/windows since we handle navigations and actions within them

nativeMessaging

Gives your extension access to the native messaging API.

Communication protocol to act with our installed adapters, it is how they communicate with each other

management

Gives your extension access to the chrome.management API.

So we can request specific permissions on actions that are not common

webNavigation

Gives your extension access to the chrome.webNavigation API.

We use it to track where does the user go interactively so we can target the correct environment

storage

Gives your extension access to the chrome.storage API.

We save information regarding the runtime of the extension itself, so we can better diagnosticate any issues

background

Makes Chrome start up early and and shut down late, so that apps and extensions can have a longer life. When any installed hosted app, packaged app, or extension has "background" permission, Chrome runs (invisibly) as soon as the user logs into their computer—before the user launches Chrome. The "background" permission also makes Chrome continue running (even after its last window is closed) until the user explicitly quits Chrome. You typically use the "background" permission with a background page, event page or (for hosted apps) a background window.

For execution purposes, the extension uses this permission to be able to start a new browser at “Launch browser” steps.

activeTab

Requests that the extension be granted permissions according to the activeTab specification.

Reads the active tab in order to set/determine the context for recording/execution