Protegrity Policy Manager on

Uninstalling the Protegrity Policy Manager

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

To uninstall the deployment:

Run the following command to uninstall the Policy Workbench.

helm uninstall policy-workbench -n policy-workbench

Run the following command to clean up the AWS resources.

tofu destroy -var='cluster_name=<PPC cluster name>'

Workbench Roles and Permissions

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

Roles are templates that include permissions and users can be assigned to one or more roles. All users in the appliance must be associated with a role.

The roles packaged with Policy Workbench are as follows:

Roles	Description	Permissions
workbench_administrator	Full administrative access to workbench.	workbench_management_policy_write, workbench_deployment_immutablepackage_export, workbench_deployment_certificate_export
workbench_viewer	Read-only access to workbench.	workbench_management_policy_read
workbench_deployment_administrator	Administrative access to workbench deployments.	workbench_deployment_immutablepackage_export, workbench_deployment_certificate_export

The capabilities of a role are defined by the permissions attached to the role. Though roles can be created, modified, or deleted from the appliance, permissions cannot be edited. The permissions that are available to map with a user and packaged with Policy Workbench as default permissions are as follows:

Troubleshooting the Protegrity Policy Manager

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

Helm upgrade fails due to existing Kubernetes jobs

Issue: Helm upgrade fails because existing jobs, such as hubcontroller-init and kmgw-create-keystore, cannot be patched.

Description: Helm upgrade cannot modify or replace existing Kubernetes jobs if fields such as image registry, environment variables, args, and volumes are changed. This happens because the pod template of a job is immutable. So, the existing pods cannot be replaced when their template changes. As a result, the Helm upgrade fails.

Upgrading Policy Workbench in AWS

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

Before you begin

Back up the existing Policy Workbench data.

For more information, refer to Backing up the Policy Workbench for AWS.

Configuring Credentials for the Policy Workbench

Perform the following steps to configure the credentials to access the Policy Workbench from the OCI registry.

Run the following command to create the configuration directory.
```
mkdir -p ~/.config/containers
```
Obtain the username and access token from the My.Protegrity portal. For more information about obtaining the credentials from the My.Protegrity portal, refer to the section Configuring Authentication for Protegrity AI Team Edition.