<?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 Rest Post mit tSetKeystore results in &amp;quot;No trusted certificate found&amp;quot; in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Rest-Post-mit-tSetKeystore-results-in-quot-No-trusted/m-p/2259935#M41247</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i have a job calling a public REST API via HTTPS. If i call this API without a tSetKeystore, i get a correct response.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are DB2 inputs and outputs too. We changed to SSL communication and added a tSetKeystore to do so.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With this Keystore the API call results in "No trusted certificate found" with the tRest component and in "unable to find valid certification path to requested target" with a tRestClient component.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So Talend tries to use this keystore in all components? Is it possible to block the usage of the keystore in the tRest / tRestClient component?&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2020 11:53:26 GMT</pubDate>
    <dc:creator>ToEckert</dc:creator>
    <dc:date>2020-05-18T11:53:26Z</dc:date>
    <item>
      <title>Rest Post mit tSetKeystore results in "No trusted certificate found"</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Rest-Post-mit-tSetKeystore-results-in-quot-No-trusted/m-p/2259935#M41247</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;i have a job calling a public REST API via HTTPS. If i call this API without a tSetKeystore, i get a correct response.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are DB2 inputs and outputs too. We changed to SSL communication and added a tSetKeystore to do so.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With this Keystore the API call results in "No trusted certificate found" with the tRest component and in "unable to find valid certification path to requested target" with a tRestClient component.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So Talend tries to use this keystore in all components? Is it possible to block the usage of the keystore in the tRest / tRestClient component?&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2020 11:53:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Rest-Post-mit-tSetKeystore-results-in-quot-No-trusted/m-p/2259935#M41247</guid>
      <dc:creator>ToEckert</dc:creator>
      <dc:date>2020-05-18T11:53:26Z</dc:date>
    </item>
  </channel>
</rss>

