PalveronPalveronDocs

Installation for one person

Issue an enrolment code, install the Browser Guard in Chrome or Edge and enrol the device. No project API key is needed.

This page shows how one person installs the Browser Guard and enrols their device. To install it for many devices at once, use Setup through device management.

The Browser Guard does not use a project API key (since version 1.6.0). A device enrols with an enrolment code; from then on, the Browser Guard signs every request with its own device key.

Before you start

  • An admin of your project issues the enrolment code. Every other role sees the section in read-only mode ("Only admins can manage enrolment codes and devices.").
  • Chrome or Edge on a desktop computer. Firefox and Safari are planned; mobile browsers are not supported.
  • The package of the Browser Guard that Palveron gives you. The entries in the Chrome Web Store and in Edge Add-ons follow after approval; there is no date yet.
  • The address of your gateway, only for your own gateway. For Palveron Cloud the address https://gateway.palveron.com is preset in the Browser Guard; you only need the enrolment code. If your organization runs its own gateway, you also need its address.

1. Issue an enrolment code (admin)

  1. In the dashboard, open Settings and the Security tab.
  2. Scroll to the Browser Guard section and then to Enrolment codes.
  3. Choose Valid for (days): 1 to 365 days, default 30.
  4. Choose the Device limit: how many devices may enrol with this code (1 to 10000, default 500).
  5. Click Issue code.
  6. The code is shown under Copy this enrolment code now. Click Copy and then Done.

The code is shown only this once. After you click Done, it cannot be shown again. If you lose it, issue a new code.

Give the code to the person who installs the Browser Guard, through a channel your organization trusts for credentials. If your organization runs its own gateway, also give them its address.

2. Install the Browser Guard (person)

  1. Unpack the package of the Browser Guard into a folder that stays on the device.
  2. Open chrome://extensions in Chrome or edge://extensions in Edge and switch on Developer mode.
  3. Select Load unpacked and choose the folder.
  4. Click the Browser Guard icon in the browser toolbar to open its window.
  5. Enter the code under Enrolment code.
  6. Only for your own gateway: open Use your own gateway and enter its address under Gateway address. Without a change, the Browser Guard connects to the Palveron Cloud.
  7. Click Enrol. The window then shows "This device is enrolled."

The Browser Guard creates a key on the device that cannot be read out, sends the public key together with the code and receives a device identifier from the gateway. The private key never leaves the device.

3. Check the device (admin)

Under Settings → Security → Devices, the device now appears with Enrolled, Last seen and Code. In the list of enrolment codes, the Devices column counts the devices that enrolled with the code.

Active installations (last 30 days) counts the devices that reported in the last 30 days, without revoked ones.

Manage codes and devices

ActionWhereEffect
Revoke a codeEnrolment codes → Revoke → Revoke codeNo new device can enrol with this code. Devices that already enrolled with it keep working.
Revoke a deviceDevices → Revoke → Revoke deviceThe device is refused from its next request. The person would have to enrol the device again.
Move a device to another projectIn the Browser Guard window, under Enrol this device again, enter a code of the other projectA different code than the one used for enrolment switches the device to the project of the new code.

A code shows one of the states Active, Revoked or Expired.

Moving from older Browser Guards

Browser Guards before version 1.6.0 were set up with the project API key. Under Settings → Security, the section Transition for older Browser Guards decides whether they may still report:

  • Open: older Browser Guards keep reporting results and visits with the project API key.
  • Closed: only enrolled devices report; the project API key no longer counts as a Browser Guard.

Close the transition once every installation runs version 1.6.0 or later and appears under Devices. Browser Guards that have enrolled a device are not affected by closing it.

Uninstall

Remove the extension through the extensions menu of Chrome or Edge. If the device should no longer count for your project, also revoke it under Settings → Security → Devices.

On this page