Once we are ready to deploy the extension, we can produce the deployment package (CRX) via the Browser's UI, from the Extensions page click 'Pack extension'. To debug the extension using the Developer Tools click on the 'Background page' link. While in development the Extension ID is a hash based on the extensions path.

You should see your extension listed under 'Form other sources' section on the extensions page.Īt this point in time, you have not signed the extension with your private key. Select the folder which contains your extension manifest and source code. ) Į.requestHeaders = userAgentOverride Ĭ(setHeaders) Ĭ(įor local testing, it's possible to side load your extension in Microsoft Edge, first enable 'Developer Mode', once enabled navigate to 'edge://extensions/' and select 'Load unpacked'. For our simple scenario create a file called manifest.json and add the following json. Create the extension manifestĮach extension requires a manifestfile which defines important information for that extension, this file is then used by the browser and the Microsoft Edge Web Store for discoverability, installation & updates. If you leverage the Private Key generated above to package your extension the resulting Extension ID will be 'gimgeafkohnmpdeopfnpankklbllicfn'. The Microsoft Edge (Chromium) Extension ID: > openssl rsa -in key.pem -pubout -outform DER | shasum -a 256 | head -c32 | tr 0-9a-f a-p MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxVF/+SPvFky9yYjTUeXbKJj6r1ZdDxoS+GGnVtYIoRCtwM3Lt1QuIWoG/t8bCNq+J5GJKm9+y5U/keDRtoDPghbCzuysJxMSmkJzb85CK1KFkxBfNAG8oAM3p1d4+jR4tudp0s9Re97OiQOqZNXhiFqQ30g1EJr/+KBe6Wyh+hKr+/9O88YMtnvUzc6595aBHRkhqvsE9x8pNKf29FBppivh/PlEDqyBeCSWYCiJNFHM0gsVIrkUaSE9RPNVSlxn2tZH8pMH1A+dpUT4d6y+nDE9SeAxBCZrG8KMQHGyZR9I6ylnar52M259Y+LUQ/U5LZWhsUsryqd4i5wuWeq5RQIDAQAB Generate the public key: > openssl rsa -in key.pem -pubout -outform DER | openssl base64 -A Generating RSA private key, 2048 bit long modulus (2 primes) Generate the private key: > openssl genrsa 2048 | openssl pkcs8 -topk8 -nocrypt -out key.pem Once we have this keypair, we are also able to generate the extension's id this is an important identifier which we will use later in the post.įor our scenario we can create a self-signed certificate with the following steps: This certificate will be used to digitally sign the extensions deployment package (CRX), we would also use this keypair for packaging subsequent extension updates. If we do not plan to distribute our extension via the Microsoft Edge Web Store, we will need a certificate. The high-level steps for building & packaging a simple extension are as follows: Before we can continue, we need a simple extension to deploy.

There are multiple steps to building a Microsoft Edge Extension, in this post I will focus on extension distribution & deployment. In this blog post I would like to explore how we can distribute our custom Microsoft Edge extensions within the Enterprise. Chromium brings with it an excellent extensibility model for customers and 3rd parties to extend the browsing experience, these extensions can also be published to the public Microsoft Edge Web Store. Microsoft decided to base the latest version of Microsoft Edge on Chromium, this results in a much more standards-based browsing experience where Microsoft can innovate in other areas like UI etc.

Chromium edge enterprise