This site requires JavaScript to be enabled
IE BUMPER

Product
Version
IncidentLookup using list
Language
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
  Help
IE BUMPER
Categories
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
AND
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Wildcards
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Phrases
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

Self-host the Tosca Chrome and Edge Chromium Extensions in an internal web server

This guide offers an alternative to distribution of the Tricentis Tosca Chrome and Edge Chromium Extensions.


Situation

The Tricentis Tosca Chrome or Edge Chromium Extension needs to be self-hosted in an internal web server because you can neither obtain it from the Chrome web store nor install it from local file. 

 

Solution

Requirements

  • Internal web server
    You need an internal web server that will host the Chrome extension and the manifest XML file.
    Note that these two files must be accessible without authentication.
  • ID and version of the Chrome extension
    To obtain these two, you must install the Chrome extension once on any machine. It does not matter if you install it from local file or from the Chrome Web Store. 
    Once installed, open Chrome and navigate to chrome://extensions/. If not done already, activate Developer Mode. Now you will be shown both the ID and the version of the extension. Note these down for later use.
  • Ability to distribute extension via Windows Group policy or via Window registry keys

 

Steps

1. Host extension

Take the Chrome extension from the Tosca installation directory and place it on your web server.

For versions up to and including 12.1, the default path to the extension is:
%TRICENTIS_HOME%/Resources/ChromeExtension/TOSCAChromeAutomation.crx

For versions higher than 12.1, the default path is: 
%TBOX_HOME%Resources\ChromeExtension

 

2. Host manifest

Create an XML file with the name manifest.xml and the following content:

<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
  <app appid='ekilpdeokbpjmminmhfcgkncmmohmfeb'>
    <updatecheck codebase='https://app.somecompany.com/chrome/helloworld.crx' version='1.0' />
  </app>
</gupdate>

Replace the appid with the ID of the extension that you noted down earlier. Replace the version with the version you noted down earlier. Also adapt the codebase parameter to point to the Chrome extension hosted on your internal web server.

This file must also be hosted on the web server.

 

3. Distribute extension

There are two ways to distribute the extenion: Windows Group Policy or Windows registry. Note that both options require elevated rights. Usually only administrators can do this. In general, it makes sense to manage these centrally so not every user has to do it themselves.

 

  • via Group Policy
    The required policy is Computer Configuration->Administrative Templates->Google->Google Chrome->Extensions->Configure the list of force-installed apps/extensions. If this policy is not available in your environment, an administrator can import the policy template from Google.
    Double click on the policy and select Enabled. Then click on Show. In the following popup enter the combination of appid and manifest.xml path as below:
    appid;path-to-manifest.xml (e.g. ekilpdeokbpjmminmhfcgkncmmohmfeb;https://app.somecompany.com/chrome/manifest.xml)
    Confirm and close the dialogs.

     
  • via Windows registry
    Navigate to the following path in the Windows registry: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist.
    Create a key with name 1. The value is the combination of appid and manifest.xml path as below:
    appid;path-to-manifest.xml (e.g. ekilpdeokbpjmminmhfcgkncmmohmfeb;https://app.somecompany.com/chrome/manifest.xml)
    Confirm and close the dialogs.

 

Edge Chromium

For Edge Chromium, the same approach applies.

However you need to pack the extension first, as the one delivered with the Tosca installation is unpacked. To do this, first copy the folder %TBOX_HOME%Resources\EdgeChromiumExtension\TOSCAEdgeAutomation to a different location. This is to ensure you have write permission to create the packed extension. Open Edge and enable Developer mode. Then click Pack extension and select the path to the folder you just copied. A .crx file will be created. Install the packed extension once in Edge Developer mode to get the version and ID.
These steps need to be done only once.

 

To download the relevant group policy template, visit the Microsoft website. Select your Edge version and click on Get policy files.

 

Reference

https://docs.google.com/document/d/1pT0ZSbGdrbGvuCsVD2jjxrw-GVz-80rMS2dgkkquhTY/edit#heading=h.gb2ntk6856ld

Attachments
0 0

Manasa Ch

Created: 2020-10-05 11:57:57

Does the same procedure work for chromebased edge