---
updatedAt: 2026-07-16T20:54:09.000Z
---

# Installer activation keys | PS Pathfinder

## Configure OAuth authentication for agents with installer activation keys

Use installer activation keys to leverage OAuth authentication when configuring:

* Endpoint Privilege Management (EPM) agents that support OAuth communications.
* Discovery Scanner event client and central policy.

A maximum of 10 installer activation keys can be present at any one time, including the system generated key. Keys can be deleted and new ones can be created as long as no more than 10 keys exist at once.

1. At the top left of the page, click ![Main menu icon](https://files.readme.io/8008765b74ecfb3975c6ad5d13f4705ec95477331afdfe9472f38b917fc0baf3-menu.png) **> Password Safe > Configuration**.\
   The **Configuration**page displays. You can also click the **Configuration** container card on the **Password Safe** page.

2. Under **Authentication Management**, select **Installer Activation Keys**.

[block:image]{"images":[{"image":["https://files.readme.io/fe4e0c362663eb139ba73a044edaf1cbd2da40e0cbebf0f791d98c8c8a5e0974-installer_activation_keys.png","",""],"align":"center"}]}[/block]

3. To use the key generated by the system:
   * Select **System Generated Key**.
   * Select an **Installer Type**: **Discovery Agent** or Endpoint Privilege Management **Agent**.
   * Copy the installation command, make any necessary edits, and use it when deploying the agent.
4. To create a new installer key:
   * Click **Create New Installer Activation Key +**.
   * Enter a name for the key.
   * Click **Create Activation Key**.
   * Select an **Installer Type**: **Discovery Agent** or Endpoint Privilege Management **Agent**.
   * Copy the installation command, make any necessary edits, and use it when deploying the agent.

When creating an installer activation key for Endpoint Privilege Management confirm the exact file name of the MSI (x86 vs x64).

> ℹ️
>
> Once the endpoint communication is established with Password Safe, the activation key is no longer required. We recommend deleting it.
>
> If you delete the key and an endpoint stops working and must be reconfigured, create a new installer activation key before uninstalling and reinstalling the client.

Activation keys and IDs are stored in the credential vault. When upgrading the endpoint in the future, the values are not required.

For example, if you initially run the Endpoint Privilege Management install using this command:

```
msiexec.exe /I PriviliegeManagementForWindows.msi /qn /norestart BI_MODE=1 BEYONDINSIGHTURL="test" ActivationId="test" ActivationKey="test"
```

Then run the upgrade using this command:

```
msiexec.exe /I PriviliegeManagementForWindows.msi /qn /norestart BI_MODE=1 BEYONDINSIGHTURL="test"
```