Create an Azure Connector with global proxy connection

Products

• CA Identity Suite

Issue/Introduction

We want to create an Azure Connector by our proxy. When we use Global Proxy configuration with our proxy information, the application cannot communicate by our proxy. The communication is provided by ASA Switch. 

How to configure IDM for communicating to Azure?

We have this errors message : 

Modify Azure Endpoint task, Azure Endpoint Azure: Modify Azure Endpoint "Azure": Failed to execute ModifyAzureEndpoint. ERROR MESSAGE: Endpoint 'Azure' modification failed: Connector Server Add failed: code 53 (UNWILLING_TO_PERFORM): failed to add entry eTDYNDirectoryName=Azure,eTNamespaceName=Azure,dc=im,dc=etasa: JCS@hostname: AzureRest: Connect to login.microsoftonline.com:443 [login.microsoftonline.com/xx.xxx.xx.1, login.microsoftonline.com/xx.xxx.xx.3, login.microsoftonline.com/xx.xxx.xx.4, login.microsoftonline.com/xx.xxx.xx.5, login.microsoftonline.com/xx.xxx.xx.6, login.microsoftonline.com/xx.xxx.xx.7, login.microsoftonline.com/xx.xxx.xx.2, login.microsoftonline.com/xx.xxx.xx.10] failed: Connection refused: connect (ldaps:/hostname.test.com:20411),

 

 

 

 

Cause

Not all connectors can use the global proxy. The JCS global proxy is not used by the Azure connector:

https://community.broadcom.com/participate/ideation-home/viewidea?IdeationKey=742e1842-f904-4ef2-bd3e-262e2ddecbe5

Content of link:

Currently, the JCS HTTP Proxy settings are not used by the Azure (REST) connector.

However, since Azure is a cloud computing service, customers that have JCS deployed on-premise and have only access to the Internet via HTTP Proxy are not able to make use of the connector.

So, all connectors to cloud services, including the Azure connector should use the HTTP Proxy or the use of the HTTP Proxy should be configurable at the endpoint level.

 

Resolution

Fixed in IM 14.3 CP3 and in IM 14.4 CP1