CA Identity manager creation failed: CA Access Control: ACC-LCA Error 0x2757: Connection to <endpoint name> for <admin user> failed for attempt number 1 of 1

Products

• CA Identity Suite

Issue/Introduction

Using Provisioning Manager, when trying to access the CA Access Control Endpoint, it fails with an error “CA Access Control Endpoint <endpoint name> creation failed: CA Access Control: ACC-LCA Error 0x2757: Connection to <endpoint name> for <admin user> failed for attempt number 1 of 1 (Error: Connection Failed
Error: Failed to receive reply.”

 

Environment

IGA V15.0

Cause

The default Encryption Pack used in CCS v15 has changed; now it is using C:\Program Files (x86)\Broadcom\Identity Manager\Connector Server\ccs\etc\acc\defenc.dll instead of the one used in older versions (up to 14.5.x) - C:\Program Files (x86)\Broadcom\Identity Manager\Connector Server\ccs\etc\acc\aes256enc.dll

Resolution

Steps to perform:

1)On the CCS Machine: Using registry editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Identity Manager\Provisioning Server\NSOptions\ACC\eTrust Access Control SDKrt and verify Encryption Package key path (ie C:\Program Files (x86)\Broadcom\Identity Manager\Connector Server\ccs\etc\acc\defenc.dll). Also, verify the same key path under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\Identity Manager\Provisioning Server\NSOptions\ACC\eTrust Access Control SDKrt

2)On the ACC Machine: Using the registry editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\AccessControl and verify the Encryption Package key path (i.e., C:\Program Files \CA\PAMSC\bin\aes256enc.dll)

3)If the DLL used by ACC is not the same one as used by the CCS, update the 2 registry settings of the CCS to use the DLL used by ACC.

4)Restart CCS

5) Now, attempt to acquire a CA Account Control machine