topic Problem activating https (SSL) for tREST Request using the talend ESB Runtime in Talend Studio

Problem activating https (SSL) for tREST Request using the talend ESB Runtime

Anonymous — Sat, 16 Nov 2024 05:07:17 GMT

Hi,

I'm still pretty new to Talend but I need some help please.

I am using Talend Open Studio for ESB (7.1.1) . I created a Job with tREST_Request offering Endpoints as a sort off REST API. Depending on the exact URL the job will return data from a database.

The Job is deployed in the talend Runtime (karaf 4.1.6). I wanted to change from http to https following this guide (https://help.talend.com/reader/T7hdMN16K129AtayaQluAA/o1KcDqJ6UICtnTMj6Ih0bA) but I only manage to reach the step where the webconsole of the karaf container is set to use https (used settings below and key generatet like in the guide).

# Default port for the OSGI HTTP Service
org.osgi.service.http.port=8040

org.osgi.service.http.port.secure=9001
org.osgi.service.http.secure.enabled=true
org.ops4j.pax.web.ssl.keystore=${karaf.base}/etc/keystores/keystore.jks
org.ops4j.pax.web.ssl.password=password
org.ops4j.pax.web.ssl.keypassword=ser23rest
#org.ops4j.pax.web.ssl.clientauthwanted=false
org.ops4j.pax.web.ssl.clientauthneeded=true
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml

Which is working just fine. After the next steps the webconsole and the job is not reachable.

So if I change the jetty.xml or the org.apache.cxf.http.conduits-common.cfg according to the guide I am not able to reach the service. Are those changes necessary? I have seen post where it was enough to change the org.ops4j.pax.web.cfg.

There are quit a few posts about the subject but not a single one worked for me.

I hope you guys can help me out.

Best regards

Re: Problem activating https (SSL) for tREST Request using the talend ESB Runtime

Anonymous — Tue, 30 Jul 2019 15:26:18 GMT

I found the solution.

In my case the settings in the jetty.xml has been incorrect or conflicting with my settings in the org.ops4j.pax.web.cfg. The settings from the mentioned guide didn't work for me. The simple sollution for me is to comment out the jetty.xml refference in the org.ops4j.pax.web.cfg.

# Default port for the OSGI HTTP Service
org.osgi.service.http.port=8040

org.osgi.service.http.port.secure=9001
org.osgi.service.http.secure.enabled=true
org.ops4j.pax.web.ssl.keystore=${karaf.base}/etc/keystores/keystore.jks
org.ops4j.pax.web.ssl.password=password
org.ops4j.pax.web.ssl.keypassword=password
# org.ops4j.pax.web.ssl.clientauthwanted=false
org.ops4j.pax.web.ssl.clientauthneeded=true
# org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml

Re: Problem activating https (SSL) for tREST Request using the talend ESB Runtime

Anonymous — Wed, 07 Aug 2019 08:11:55 GMT

Hello,

Thanks for letting us know that you have resolved this issue by yourself.

Best regards

Sabrina