<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pre-Configuration on</title><link>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/</link><description>Recent content in Pre-Configuration on</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Extension Source Code</title><link>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/prepare_extension/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/prepare_extension/</guid><description>Setting up the Browser Protector Extension For Distribution Before deploying the Protegrity Browser Protector extension in your organization, you must set up the extension source code for secure distribution. This involves signing the extension and packaging it into a .crx file, which can then be distributed to users or deployed via MDM tools like Microsoft Intune.
Signing the extension ensures its integrity and authenticity, allowing browsers to verify that the extension has not been tampered with and originates from a trusted source.</description></item><item><title>Host Extension On Private Server</title><link>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/https_file_hosting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/https_file_hosting/</guid><description>Prepare the .crx File Ensure you have the .crx file for Protegrity Browser Protector extension. If you haven’t created one yet, follow the steps in the Extension Source Code section.
Set Up HTTPS File Hosting HTTPS File hosting service is required to host the .crx file. This can be any web server, such as, Apache, Nginx, or a cloud storage service.
Set Up an Amazon S3 Bucket Create a new S3 bucket:</description></item><item><title>Entra ID Configuration</title><link>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/sso_ms_entra_id/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/sso_ms_entra_id/</guid><description>Configuring Entra ID Single Sign-On (SSO) for Protegrity Browser Protector To enable SSO using Microsoft Entra ID, formerly Azure AD, for the Protegrity Browser Protector extension, follow the steps below.
Create a New App Registration Log in to the Microsoft Entra Admin Center. Navigate to App registrations &amp;gt; New registration. Provide the following details for the new app: Name: Enter a name for the app, for example, Protegrity Browser Protector. Supported account types: Choose the account type suitable for your organization.</description></item><item><title>Set Up Configuration File for Browser Protector</title><link>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/config_file/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/browser-protector/1.0.2/docs/installation/pre_configuration/config_file/</guid><description>Configuring the Protegrity Browser Protector The Protegrity Browser Protector can be customized and managed using a configuration file in JSON format distributed via MDM tools described in the installation chapters. The configuration file defines key settings, such as the service endpoint for tokenization, authentication service configuration, the data elements to be used to protect clear text values as well as administrative contact information display in the Browser Protector Extension.
Configuration File Overview Below is an example configuration file for the Protegrity Browser Protector:</description></item></channel></rss>