Upgrading the Agent to v1.2.0 on

Migrating conversation ownership

Mon, 01 Jan 0001 00:00:00 +0000

Protegrity Agent v1.0 does not track conversation ownership. All users with access to the Agent share a single pool of conversations.

Protegrity Agent 1.2.0 introduces per-user conversation ownership. As a result, conversations are visible only to their respective owners.

Because Agent v1.0 did not record the original creator of each conversation, the migration process cannot restore conversations to their original owners.

To migrate the ownership, select one of the following options:

Preparing database credentials

Mon, 01 Jan 0001 00:00:00 +0000

The helm chart v2.0.0 requires a pre-existing database credentials Secret and no longer creates the Secret from Helm values during installation.

For upgrades from Helm chart v1.1.0, the Helm-managed database-secrets resource is retained and can continue to use its default name. Helm chart v1.0.0 does not retain this Secret.

The following procedure creates a new unmanaged Secret by copying the existing database credentials. The procedure is applicable to upgrades from either version. It copies the encoded Secret data without exposing the database password in command output.

Upgrading the Agent to v1.2.0

Mon, 01 Jan 0001 00:00:00 +0000

Before you begin

Ensure that the PPC is upgraded to v1.2.0.
Verify that the platform publishes the application-node machine type required by chart 2.0.0, using the following command:
```
kubectl get configmap nfa-config -n default \
-o jsonpath='{.data.CLOUD_VENDOR}{"\t"}{.data.ARCHITECTURE}{"\t"}{.data.USERPOOL_INSTANCE_TYPE}{"\n"}'
```
Do not proceed with the upgrade if the machine type is empty. Using a PPC user credentials, update the PPC ConfigMap to specify a valid machine type. Alternatively, provide a machine type override by adding the following parameter to both Helm commands used during the upgrade:

Decommissioning the connection to PIM

Mon, 01 Jan 0001 00:00:00 +0000

Protegrity Agent v1.2.0 does not connect to a live PIM tenant. Agent responses are generated exclusively from the bundled Traverse and Policy product documentation.

The Agent operates in a read-only mode and does not perform create, modify, or delete operations against any Protegrity product. As a result, workflows in Agent v1.0 that depended on the Agent executing PIM operations are not supported in Agent v1.2.0.

As part of the upgrade, remove any PIM-specific endpoint configurations, credentials, and network egress rules that were provisioned solely for the Agent v1.0 integration.

Migrating users

Mon, 01 Jan 0001 00:00:00 +0000

Agent access definitions are reapplied during every helm upgrade through the ProductConfiguration custom resource.

User-to-role assignments stored in the PPC authentication layer are not migrated automatically. Before removing any legacy assignments, assign the replacement Agent roles to all existing user accounts and verify that each user can successfully sign in and access the Agent.

Remove the legacy role assignments only after validating that the new assignments function as expected for all users.