PKIX path validation failed With Datahub 6.6

[Former Member]

We are getting following exception while publishing from datahub to hybris

Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed

We are upgrading from 5.6 (hybris + DH) to 6.6 (hybris + DH)

Here are datahub (local.properties) entries :

         datahub.security.https.enabled=false
        datahubadapter.security.https.enabled=false
        datahub.security.ssl.trustStore=classpath:datahub.jks
       datahub.security.ssl.trustStorePassword=123456

Hybris local.property has following entry

       datahubadapter.security.https.enabled=false

[Former Member · Accepted solution]

I had changed ports for my hybris (http:13001 and SSL:13002 etc). in datahub properties files after I set datahub.core.export.service.oauth.port=13002 (same as SSL port).

With this change I was successfully able to able to publish items to hybris from datahub. To understand that I need to specify oAuth port (same as SSL port), evenif I have disabled https by using datahub.security.https.enabled=false. I had to debug datahub code as I could not find this in any document help.

[Former Member]

I am using 6.6.0.0 hybris and 6.6.0.4-RC1 datahub. I had another hybris instance (5.6 version) running on same box (offcourse in different port). After I stopped the 5.6 instance, now the error has changed a bit like following :

com.hybris.datahub.api.publication.PublicationException: An error occurred during the export of impex file at com.hybris.datahub.core.adapter.impl.DefaultCoreAdapterPublicationService.targetSystemPublication(DefaultCoreAdapterPublicationService.java:61) at com.hybris.datahub.core.adapter.impl.DefaultCoreAdapterPublicationService.publish(DefaultCoreAdapterPublicationService.java:39) at com.hybris.datahub.core.adapter.impl.CoreAdapterService.publish(CoreAdapterService.java:77) at com.hybris.datahub.service.publication.impl.DefaultDataHubPublicationService.startPublication(DefaultDataHubPublicationService.java:255) at com.hybris.datahub.service.publication.impl.DefaultDataHubPublicationService.publish(DefaultDataHubPublicationService.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)

Caused by: javax.ws.rs.ProcessingException: java.net.ConnectException: Connection refused at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:287) at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:252) at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:684) at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:681) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:681) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:437)

Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

[former_member333910]

I larger excerpt of the stack trace from the error would be helpful.

Setting datahub.security.https.enabled=false should result in the Data Hub using the NoopHostnameVerifier and I wouldn't expect any handshake errors.

However, I'm not familiar with the "timestamp check failed" and I'm curious if you are using version 6.6 for both Data Hub and Hybris Platform.