cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

service registration on Kyma

former_member903086
Discoverer
0 Likes
919

Hi, I'm trying to setup hybris in order to interact with Kyma. I have a Kyma instance up and running and I'm following these Hybris guides below and I have some questions about them:

Setup guide

https://help.hybris.com/1808/hcd/cdd6c450a2f24f56961c02edb070f1c4.html

  • the step 2 asks about a real certificate not a self signed one: is this only for production? Or does it affect also the development?

One click integration guide

https://help.hybris.com/1808/hcd/01c870c2c21448c6bffb8412bc2d5038.html#loio01c870c2c21448c6bffb8412b...

  • in step 4 I successfully retrieve the certificate but the api registration fails with this error:

    ERROR [hybrisHTTP28] [KymaApiRegistrationStrategy] Failed to register Exposed Destination in kyma with URL: [{https://gateway.kyma.local/ec-default/v1/metadata/services}] ERROR [hybrisHTTP28] [RetrieveCertificateController] de.hybris.platform.apiregistryservices.exceptions.ApiRegistrationException: Failed to register Exposed Destination in kyma with URL: [{https://gateway.kyma.local/ec-default/v1/metadata/services}]

       org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://gateway.kyma.local/ec-default/v1/metadata/services": sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    
    

I'm wondering if the problem is the certificate validation since the only service I could register was done without checking the certificate from command line:

 http POST https://gateway.kyma.local:${NODE_PORT}/ec-default/v1/metadata/services --cert=generated.pem --verify=no < hybrisService.json

So my questions are:

  • is it possible to use kyma and hybris without a real certificate?

  • is it possible to disable from hybris the certificate check for development purpose?

Thanks

Accepted Solutions (0)

Answers (3)

Answers (3)

srihitha
Explorer
0 Likes

Hi @a.spiggia

Could you please send the reference to integrate kyma with hybris as i am unable to find one. Links which you referenced https://help.hybris.com/1808/hcd/cdd6c450a2f24f56961c02edb070f1c4.html is not working now.

vks_414
Discoverer
0 Likes

Hi , were you able to fix this error ? facing same issue if you can please help on this ... i am trying to connect hybris with kyma installed on Google cloud platform .


Caught throwable I/O error on GET request for "https://gateway.35.188.17.122.xip.io/v1/applications/management/info": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://gateway.35.188.17.122.xip.io/v1/applications/management/info": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:744) at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:670) at org.springframework.web.client.RestTemplate.getForObject(RestTemplate.java:311) at de.hybris.platform.kymaintegrationservices.jobs.KymaUpdateConsumedDestinationsJobPerformable.perform(KymaUpdateConsumedDestinationsJobPerformable.java:105) at de.hybris.platform.servicelayer.internal.jalo.ServicelayerJob.performCronJob(ServicelayerJob.java:38) at de.hybris.platform.cronjob.jalo.Job.execute(Job.java:1376) at de.hybris.platform.cronjob.jalo.Job.performImpl(Job.java:803) at de.hybris.platform.cronjob.jalo.Job$JobRunable.run(Job.java:672) at de.hybris.platform.util.threadpool.PoolableThread.internalRun(PoolableThread.java:206) at de.hybris.platform.core.threadregistry.RegistrableThread.run(RegistrableThread.java:131) Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:128) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:321) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:259) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:642) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.onCertificate(CertificateMessage.java:461) at java.base/sun.security.ssl.CertificateMessage$T12CertificateConsumer.consume(CertificateMessage.java:361) at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:421)

Former Member
0 Likes

Hi, I had the same problem and managed to fix it adding kyma certificate into my java keystore:

 sudo {JAVA_HOME}/bin/keytool -import -alias “Kyma” -keystore {JAVA_HOME}/jre/lib/security/cacerts -file <KYMA_HOME>/installation/certs/workspace/raw/server.crt

See https://kyma-project.io/docs/components/application-connector > Access the Application Connector on a local Kyma deployment for more info