<?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 BOX connection from Talend Studio and Cloud in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/BOX-connection-from-Talend-Studio-and-Cloud/m-p/2270301#M48260</link>
    <description>&lt;P&gt;I am looking for documentation how to successfully connect from BOX to retrieve files.&lt;/P&gt;
&lt;P&gt;We normally connect to BOX using SSO. I created an APP in BOX which gives me&lt;/P&gt;
&lt;P&gt;1. Client ID&lt;/P&gt;
&lt;P&gt;2. Client Secret&lt;/P&gt;
&lt;P&gt;3. Primary token&lt;/P&gt;
&lt;P&gt;4. Secondary token&lt;/P&gt;
&lt;P&gt;using these and my user credentials I have to use postman to generate access token and refresh token to use inside tboxconnection.&lt;/P&gt;
&lt;P&gt;These tokens are dynamic and change frequently.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once we publish the job to cloud, there we have entirely different option. It just needs my userid password to connect to box and no longer need any secrets, tokens.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have any one actively using this feature. Is it worth trying or should we stick to legacy FTPs?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thankyou&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 02:51:49 GMT</pubDate>
    <dc:creator>venkat5121</dc:creator>
    <dc:date>2024-11-16T02:51:49Z</dc:date>
    <item>
      <title>BOX connection from Talend Studio and Cloud</title>
      <link>https://community.qlik.com/t5/Talend-Studio/BOX-connection-from-Talend-Studio-and-Cloud/m-p/2270301#M48260</link>
      <description>&lt;P&gt;I am looking for documentation how to successfully connect from BOX to retrieve files.&lt;/P&gt;
&lt;P&gt;We normally connect to BOX using SSO. I created an APP in BOX which gives me&lt;/P&gt;
&lt;P&gt;1. Client ID&lt;/P&gt;
&lt;P&gt;2. Client Secret&lt;/P&gt;
&lt;P&gt;3. Primary token&lt;/P&gt;
&lt;P&gt;4. Secondary token&lt;/P&gt;
&lt;P&gt;using these and my user credentials I have to use postman to generate access token and refresh token to use inside tboxconnection.&lt;/P&gt;
&lt;P&gt;These tokens are dynamic and change frequently.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once we publish the job to cloud, there we have entirely different option. It just needs my userid password to connect to box and no longer need any secrets, tokens.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have any one actively using this feature. Is it worth trying or should we stick to legacy FTPs?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thankyou&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 02:51:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/BOX-connection-from-Talend-Studio-and-Cloud/m-p/2270301#M48260</guid>
      <dc:creator>venkat5121</dc:creator>
      <dc:date>2024-11-16T02:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: BOX connection from Talend Studio and Cloud</title>
      <link>https://community.qlik.com/t5/Talend-Studio/BOX-connection-from-Talend-Studio-and-Cloud/m-p/2270302#M48261</link>
      <description>In Talend, you can use tRest to call API to get the access token or refresh token. I have achieve similar requirement. 
&lt;BR /&gt;Normally, the access token will expires in 24 hours, so you should schedule the job to run at least one time within 24 hours to get the refresh token.
&lt;BR /&gt;
&lt;BR /&gt;Regards
&lt;BR /&gt;Shong</description>
      <pubDate>Fri, 27 Mar 2020 01:23:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/BOX-connection-from-Talend-Studio-and-Cloud/m-p/2270302#M48261</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-03-27T01:23:01Z</dc:date>
    </item>
  </channel>
</rss>

