This content provides information about the 3.3.1.09 hotfix.
This hotfix resolves the following issue:
- Errors occur after upgrading to 3.3: "Can't accept SSL cert on PAM 3.3" and "Cannot decide Access type" (Internal defect ID: DE439635).
Do the following tasks before installing this patch:
- Verify that yourSymantec Privileged Access Managerenvironment is at 3.3.1You can install this hotfix regardless of any other 3.3.1.xx hotfixes that you may have applied.
- Download CAPAM_3.3.1.09.p.zip from theSymantec Privileged Access ManagerSolutions and Patches page.
- Extract the hotfix binary, CAPAM_3.3.1.09.p.bin.
Install the 3.3.1.09 Hotfix
The hotfix should take less than a minute to install on each server.
Installing this hotfix does not require you to restart your cluster (if applicable) or cause a reboot of PAM Servers.
Do the following steps before you install the hotfix:
- To prevent logins toSymantec Privileged Access Managerduring configuration changes, turn on Maintenance Mode. Maintenance Mode is not required, but it stops disruptions from user activity.To enable Maintenance Mode:
- Select Configuration, Diagnostics, System.
- On the Modes page, turn on Maintenance Mode.
Follow these steps on
each serverin your environment (including all nodes in a cluster):
- Log in to the UI as an administrator with Global Administrator permissions.
- Navigate toConfiguration, Upgrade.
- On the Patches page, selectChoose Fileand browse to the location of the patch file on your local system.
- SelectUpload and Apply.During the upload, you might temporarily see a blank page. The hotfix gets installed.
- Verify that the hotfix installation is successful. Look for a message at the top of the page that indicates upgrade success. Also, ensure theUpgrade Historylists the patch and the date and time it was applied. If you do not see this information, contactBroadcom Supportfor further instructions.
- Log out from the UI.
- Log back in to the UI and verify that you can access devices on the Access page.
After you successfully apply this hotfix, complete the following steps:
- If applicable, turn off Maintenance Mode.
- Instruct all users who connect to the appliance through a browser to clear their Java caches before they log in again.