Inbound Notification with SSL/TLS fails with [rc=27] SSL: couldn't create a context, Originated from: .\EtaNotifyTools.cpp [1081]

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

The process documented in https://comm.support.ca.com/kb/how-do-i-configure-inbound-notifications-via-https/kb000054198 was followed in order to enable inbound synchronization with SSL/TLS and the environment is not processing the records.

The etanotify.log shows messages similar to these:
              
               20180612:160816:TID=0012e4:D: Sending Payload (1429 bytes)...

20180612:160816:TID=0012e4:D: URL(https://qaims.mywebsite.com/iam/im/ETACALLBACK/?env=idv): No need to encrypt the payload

20180612:160816:TID=0012e4:I: Try sending payload to https://qaims.mywebsite.com/iam/im/ETACALLBACK/?env=idv

20180612:160816:TID=0012e4:E: FAILED(https://qaims.mywebsite.com/iam/im/ETACALLBACK/?env=idv): [rc=27] SSL: couldn't create a cont

20180612:160816:TID=0012e4:E:+ext: (nil)

20180612:160816:TID=0012e4:E: Error in notification processing: Reason: Operation failed. ALERT: Unable to contact any IMS. Processi

20180612:160816:TID=0012e4:E:+ng aborted.

20180612:160816:TID=0012e4:E: Originated from: .\EtaNotifyTools.cpp [1081].

20180612:160816:TID=0012e4:I: DONE: Notifications Processed: 0/100+ [FAILED]

 

Environment

Identity Manager 14.2,  Provisioning Server

Resolution

This issue was found in IM 14.2 Provisioning Server and will be resolved in subsequent cumulative patch.

 A hotfix for 14.2 (no CP) comprised of  EtaNotifyTools.dll and libcurl.dll may be available. Please contact Support in reference to Hotfix DE369927