<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Connecting via tRestClient to endpoint with self-signed certificate in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310401#M81533</link>
    <description>&lt;P&gt;Can you elaborate on this? &lt;/P&gt;&lt;P&gt;I added the truststore path and password to my tRestClient as parameters and did not get any change in behaviour.&lt;/P&gt;</description>
    <pubDate>Wed, 12 May 2021 10:52:01 GMT</pubDate>
    <dc:creator>Teguard_Dev</dc:creator>
    <dc:date>2021-05-12T10:52:01Z</dc:date>
    <item>
      <title>Connecting via tRestClient to endpoint with self-signed certificate</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310397#M81529</link>
      <description>&lt;FONT size="1"&gt;&lt;FONT face="Verdana, Helvetica, Arial, sans-serif"&gt;Hello!&lt;BR /&gt;(Currently using Talend OS Big Data, 6.1.1)&lt;BR /&gt;I am struggling to connect to a RESTful API using the tRestClient, which has a self-signed root certificate. Is it possible for me to set my Talend environment up to trust the certificate? (i tried creating a truststore from the certificate and using tSetKeystore, but haven't had any luck).&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;BR /&gt; 
&lt;FONT size="1"&gt;&lt;FONT face="Verdana, Helvetica, Arial, sans-serif"&gt;Alternatively, is there a way I can set my job to disableCNCheck? I've seen some JIRA issues requesting this functionality, but I'm looking for a workaround if at all posible.&amp;nbsp;&lt;/FONT&gt;&lt;/FONT&gt;</description>
      <pubDate>Mon, 18 Jul 2016 20:03:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310397#M81529</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2016-07-18T20:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting via tRestClient to endpoint with self-signed certificate</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310398#M81530</link>
      <description>Error Message: 
&lt;BR /&gt;Exception in component tRESTClient_3 
&lt;BR /&gt;javax.ws.rs.ProcessingException: javax.net.ssl.SSLProtocolException: SSLProtocolException invoking https://&amp;lt;url-replaced-for-talendforge-post&amp;gt; actiondefinitions: handshake alert: &amp;nbsp;unrecognized_name 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.AbstractClient.checkClientException(AbstractClient.java:582) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.AbstractClient.preProcessResult(AbstractClient.java:564) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1144) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1094) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:894) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:865) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:428) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.get(WebClient.java:611) 
&lt;BR /&gt;at eai.vrealizeops_0_1.vRealizeOps.tRESTClient_3Process(vRealizeOps.java:509) 
&lt;BR /&gt;at eai.vrealizeops_0_1.vRealizeOps.runJobInTOS(vRealizeOps.java:770) 
&lt;BR /&gt;at eai.vrealizeops_0_1.vRealizeOps.main(vRealizeOps.java:627) 
&lt;BR /&gt;Caused by: javax.net.ssl.SSLProtocolException: SSLProtocolException invoking https://&amp;lt;url-replaced-for-talendforge-post&amp;gt;: handshake alert: &amp;nbsp;unrecognized_name 
&lt;BR /&gt;at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
&lt;BR /&gt;at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) 
&lt;BR /&gt;at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) 
&lt;BR /&gt;at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) 
&lt;BR /&gt;at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) 
&lt;BR /&gt;at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) 
&lt;BR /&gt;at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.AbstractClient.doRunInterceptorChain(AbstractClient.java:649) 
&lt;BR /&gt;at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1093) 
&lt;BR /&gt;... 7 more 
&lt;BR /&gt;Caused by: javax.net.ssl.SSLProtocolException: handshake alert: &amp;nbsp;unrecognized_name 
&lt;BR /&gt;at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
&lt;BR /&gt;at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) 
&lt;BR /&gt;at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) 
&lt;BR /&gt;at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1676) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1674) 
&lt;BR /&gt;at java.security.AccessController.doPrivileged(Native Method) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1672) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1245) 
&lt;BR /&gt;at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468) 
&lt;BR /&gt;at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) 
&lt;BR /&gt;at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.processRetransmit(HTTPConduit.java:1424) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRetransmits(HTTPConduit.java:1411) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1545) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) 
&lt;BR /&gt;... 13 more 
&lt;BR /&gt;Caused by: javax.net.ssl.SSLProtocolException: handshake alert: &amp;nbsp;unrecognized_name 
&lt;BR /&gt;at sun.security.ssl.ClientHandshaker.handshakeAlert(ClientHandshaker.java:1380) 
&lt;BR /&gt;at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1972) 
&lt;BR /&gt;at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1086) 
&lt;BR /&gt;at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332) 
&lt;BR /&gt;at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359) 
&lt;BR /&gt;at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343) 
&lt;BR /&gt;at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563) 
&lt;BR /&gt;at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301) 
&lt;BR /&gt;at sun.net.www.protocol.http.HttpURLConnection.getHeaderFields(HttpURLConnection.java:2714) 
&lt;BR /&gt;at sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderFields(HttpsURLConnectionImpl.java:283) 
&lt;BR /&gt;at org.apache.cxf.transport.http.Headers.readFromConnection(Headers.java:257) 
&lt;BR /&gt;at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.updateCookiesBeforeRetransmit(URLConnectionHTTPConduit.java:297) 
&lt;BR /&gt;at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRetransmits(HTTPConduit.java:1409) 
&lt;BR /&gt;... 15 more 
&lt;BR /&gt; disconnected 
&lt;BR /&gt;Job vRealizeOps ended at 13:44 18/07/2016.</description>
      <pubDate>Mon, 18 Jul 2016 20:16:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310398#M81530</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2016-07-18T20:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting via tRestClient to endpoint with self-signed certificate</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310399#M81531</link>
      <description>Hi Gabby, 
&lt;BR /&gt;I'm trying to do exactly the same... without success&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt; 
&lt;BR /&gt;To share a little more, I also tried to put the URL of the WS directly in Chrome, entering login/pwd as asked and it worked. I got the JSON response. 
&lt;BR /&gt;I guess that Chrome automatically does the SSL handshake. 
&lt;BR /&gt;When I get the response I have tryed to export the SSL certificate in Chrome to use it with the Talend tSetKeystore with no luck because it is a different format. 
&lt;BR /&gt;I think that the thing that we need is how to deal with the SSL handshake in Talend. 
&lt;BR /&gt;If someone could help us about this, it could be nice!</description>
      <pubDate>Wed, 20 Jul 2016 16:29:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310399#M81531</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-07-20T16:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting via tRestClient to endpoint with self-signed certificate</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310400#M81532</link>
      <description>Hi Gabby, 
&lt;BR /&gt;I have found the solution by my self (with google help 
&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009MA9p.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/138034i5F552429DA646D6F/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009MA9p.png" alt="0683p000009MA9p.png" /&gt;&lt;/span&gt;). 
&lt;BR /&gt;I got a better understanding of the subject after reading this article: 
&lt;BR /&gt;add-list-certficates-java-keystore.html on javarevisited.blogspot.fr (2012/03) 
&lt;BR /&gt;(the forum does not want me to post link directly) 
&lt;BR /&gt;So I did the adding on my local Java KeyStore. 
&lt;BR /&gt;Put a&amp;nbsp;tRESTClient on my Talend job. 
&lt;BR /&gt;Enterer parameters (Trustore path's and password). 
&lt;BR /&gt;Linked it to the tRESTClient component. 
&lt;BR /&gt;Launched the job and it worked!!!&amp;nbsp; 
&lt;BR /&gt;Solved for me&amp;nbsp; 
&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009MACn.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/154443iC5B8CACEF3D12C6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009MACn.png" alt="0683p000009MACn.png" /&gt;&lt;/span&gt; 
&lt;BR /&gt;So let's thank&amp;nbsp;Javin Paul for his excelent post!</description>
      <pubDate>Thu, 21 Jul 2016 08:12:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310400#M81532</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-07-21T08:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting via tRestClient to endpoint with self-signed certificate</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310401#M81533</link>
      <description>&lt;P&gt;Can you elaborate on this? &lt;/P&gt;&lt;P&gt;I added the truststore path and password to my tRestClient as parameters and did not get any change in behaviour.&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2021 10:52:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Connecting-via-tRestClient-to-endpoint-with-self-signed/m-p/2310401#M81533</guid>
      <dc:creator>Teguard_Dev</dc:creator>
      <dc:date>2021-05-12T10:52:01Z</dc:date>
    </item>
  </channel>
</rss>

