ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

PAM client is not getting launched using explicit proxy settings with exceptions

book

Article ID: 226544

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

In a system where the Symantec PAM Client is configured to use the system proxy settings

and the system proxy is configured to contain a list of exceptions

The CA PAM Client will fail to launch. Clicking on the CA PAM Client will result in a process being launched (which can be verified by accessing the Task Manager and looking for the CA PAM Client process), but no GUI will show up

Cause

When the system is configured to use a proxy, the checkbox "Use the same proxy server for all protocols" is checked by default

However, using a proxy for sockets is not supported in PAM. If this option is checked, the system will try to use it and this may result in the behaviour observed

Environment

CA Privileged Access, all versions

Resolution

If using the system proxy with exceptions is needed, please make sure that the Use the same proxy server for all protocols checkbox is unchecked in the Advanced settings window of the Internet Options for your system

Attachments