Despite that the vague error, Remote host closed connection during handshake, maybe a result of multitude of possible reasons, the reason why this is occurring is because the remove client is dropping the connection.
I notice this issue once the WLS admin was restarted after the schedule task became unresponsive and remaining in the Interrupt status despite that I bounced the WLS managed server.
While integrating OIM 11g with the ICF connector resource for reconciliation, I would often get the following error, javax.servlet.ServletException: java.lang.InstantiationError: java.lang.VirtualMachineError after a couple of attempts:
When integrating the Shibboleth IDP and the Shibboleth SP, I would receive the following saml2 metadata issue
The system encountered an error at
To report this problem, please contact the site administrator at root@localhost.
Please include the following message in any email:
opensaml::saml2md::MetadataException at (http://HOSTNAME/secure/)
Unable to locate metadata for identity provider (https://HOSTNAME/idp/shibboleth)
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM.
The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector.
However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users
This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.