Chrome Policy Deployment via .plist

Deploying the Keeper Browser Extension to Chrome via .plist Policy

Create a Keeper plist policy configuration file

If you do not have a policy file created, create your Keeper .plist policy file in your desired location (e.g., /tmp) and name it com.google.Chrome.plist. To open Terminal, select Go from the macOS menu bar, then select Utilities > Terminal.

macOS Terminal Utility

Copy and paste the contents below into your Terminal, and press Return. This will create your .plist file within the /tmp directory and display that the file is there.

Mac Terminal

cd /tmp
touch com.google.Chrome.plist
ls -la

plist file creation

In your preferred file editor or basic file editor, copy, paste and save the contents, below, into the com.google.Chrome.plist file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
	<dict>
		<key>ExtensionSettings</key>
		<dict>
			<key>bfogiafebfohielmmehodmfbbebbbpei</key>
			<dict>
				<key>installation_mode</key>
				<string>force_installed</string>
				<key>update_url</key>
				<string>https://clients2.google.com/service/update2/crx</string>
			</dict>
		</dict>
                <key>ExtensionPolicies</key>
		<!-- Chrome policies should be outside of ExtensionSettings -->
		<key>PasswordManagerEnabled</key>
		<false/>
		<key>AutofillCreditCardEnabled</key>
		<false/>
		<key>AutofillAddressEnabled</key>
		<false/>
	</dict>
</plist>

Deploying your PLIST Policy

There are multiple tools to deploy your PLIST policy. In the next set on instructions, we will walk through deploying your PLIST policy file via Jamf Pro, AirWatch and Microsoft Intune.