JCS does not use the configured HTTP proxy and issues while creating an Azure endpoint
search cancel

JCS does not use the configured HTTP proxy and issues while creating an Azure endpoint

book

Article ID: 246249

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

The customer has defined an HTTP proxy in the Java Connector Server, to acquire an Azure endpoint.

When creating the endpoint in the Identity Manager User Console, the following error is returned:

Environment

Identity Manager 14.4.1

Cause

To use the HTTP proxy in the Java Connector Server, we need to include the username and password in the server_jcs.properties file as the code expects them.

Resolution

We need to ensure httpProxyPrimary.username and httpProxyPrimary.password are present with a suitable password in the file with full path: opt\CA\Identity Manager\Connector Server\jcs\conf\override\server_jcs.properties, as mentioned below,

httpProxyConfiguration.enabled=true
httpProxyPrimary.host=99.99.99.99
httpProxyPrimary.port=8080
httpProxyPrimary.username=User1
httpProxyPrimary.password=Password1

Additional Information

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-management-and-governance-connectors/1-0/connectors/microsoft-connectors/microsoft-azure.html