OIM AD Issue - javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

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.
August 5, 2015
OIM-11gkeystoresAD
https://technicalconfessions.com/images/postimages/postimages/_404_1_SSL handshare issue OIM AD connector server.png

The remote server is dropping the connection though the specific reason on why it's getting dropped it something we need to discover. The full error is as follows: org.identityconnectors.framework.common.exceptions.ConnectorException: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake.


Check the connection

It's fairly safe to state that the connection between the servers is correct though it's probably worth determining the ping/telnet request between the servers as well as ensuring that your services are running on the remote server by performing a netstat


Check the certificate is still valid

Probably not the first thing to check though you need to ensure that your certificate remains valid. Assuming that you've already setup the connector server with SSL = true. If you're not using SSL and you have your connector server and AD IT resource setting to SSL, then you need to change that, purge the OIM cache, then retry.

If you haven't done this already, you can follow, Configuring SSL Between Oracle Identity Manager and Connector Server. This is pretty accurate with enough detail on how to import the certificate.

To confirm the certificate is valid, you need to perform the keytool command with the list parameter. A useful reference link, Common java keytool commands will be of assistance as you'll be using the OOTB java SDK keytool commands. An example to see the certificates is as follows:
./keytool -list -keystore /u01/app/oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -storepass DemoTrust -alias mykey -v


Check the remote server

Certificate is valid, OK good. Next, check the remote server itself. The connector server services has already been checked when you performed the action within the 'checking the connection' section though you need to ensure the connector server is up and running

The issue from my experience was that the HDD reached full capacity. This was a result of the connector server growing to the point that the HDD was full. The resultant action was to cleanup the HDD then bounce the services as mentioned above, including the OIM connector server service.

This however didn't resolve the issue. Once I did that, I needed to restart the Active Directory Web Services services, the remote registry service, and of course the connector server connection.

Once completed, check within the connector server logs that the connection from OIM is initiated and presented within the log file


Further Issues - Authentication failed because the remote party has closed the transport stream.

One of the reasons why the logs were getting populated was because of the following error. The error in question was getting getting populated within the ICF connector server log file at every 5 second intervals. (It's probably worth noting that the with the connector server service residing on the Active Directory Domain Controller). Obviously the SSL configuration is the immediate item in question here. The work around to this was to configure the OIM and AD IT Resource to non-ssl, which removed the error within the logs. Futhermore, this also stopped the sporadic failure for the provisioning of AD accounts. The error, 'ConnectorServer.exe Error: 0 : Error processing request' seems to be a generic response by default so I would ignore that. Of course from OIM to the connector works as expected. From the OIM perspective, the JKS had a valid certificate for the initial request. Because OIM uses the common java keystore for it's certificates, you can use the common command to validate the certificates. You'll find that this website, The Most Common Java Keytool Keystore Commands contains pretty much all the commands needed. To access the keystore though, you would use something as follows: ./keytool -list -keystore /u01/app/oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -alias mykey -v This only leaves the issue of certifications and the initial handshake over the network to be the cause to the issue, If I find out I'll re-post though for now, we're proceeding with non-SSL in our non-PROD environment

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
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.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...