<?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: tGoogleConnection and the refresh token in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355020#M120865</link>
    <description>So the refresh token is a way to authorise requests for new authentication tokens to the selected google api not itself an authentication token for that api?</description>
    <pubDate>Mon, 25 Sep 2017 14:31:00 GMT</pubDate>
    <dc:creator>mobmsc2</dc:creator>
    <dc:date>2017-09-25T14:31:00Z</dc:date>
    <item>
      <title>tGoogleConnection and the refresh token</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355018#M120863</link>
      <description>&lt;P&gt;Using the following documentation I have been able to connect to a google drive account. I understand the token is set to expire after 3600 seconds and according to the google developers oauth 2.0 playground. "&lt;SPAN&gt;The OAuth Playground does not store refresh tokens"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can someone explain the purpose of the refresh token and whether it can be used as the "access token" for the tGoogleConnection component as a way to overcome the expiration of the access token?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 14:11:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355018#M120863</guid>
      <dc:creator>mobmsc2</dc:creator>
      <dc:date>2017-09-25T14:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: tGoogleConnection and the refresh token</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355019#M120864</link>
      <description>&lt;P&gt;I wrote a tutorial about this a while ago (&lt;A href="https://www.rilhia.com/tutorials/using-oauth-20-talend-access-google-apis" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.rilhia.com/tutorials/using-oauth-20-talend-access-google-apis&lt;/A&gt;). Take a look. It may help you out with a process to use the Refresh Token.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 14:17:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355019#M120864</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-25T14:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: tGoogleConnection and the refresh token</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355020#M120865</link>
      <description>So the refresh token is a way to authorise requests for new authentication tokens to the selected google api not itself an authentication token for that api?</description>
      <pubDate>Mon, 25 Sep 2017 14:31:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355020#M120865</guid>
      <dc:creator>mobmsc2</dc:creator>
      <dc:date>2017-09-25T14:31:00Z</dc:date>
    </item>
    <item>
      <title>Re: tGoogleConnection and the refresh token</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355021#M120866</link>
      <description>&lt;P&gt;Essentially, yes. It is useful to you since once you have carried out the first authentication you do not need to go through the process that requires a human again. However you must keep the Refresh Token and your other credentials secret.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 14:36:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355021#M120866</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-09-25T14:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: tGoogleConnection and the refresh token</title>
      <link>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355022#M120867</link>
      <description>&lt;P&gt;Hi @rhall,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have same issue, I need to refresh my GCP token, your link it seems broken, can you please provide us.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;aj&lt;/P&gt;</description>
      <pubDate>Wed, 10 Mar 2021 23:28:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/tGoogleConnection-and-the-refresh-token/m-p/2355022#M120867</guid>
      <dc:creator>AJ_Sheikh</dc:creator>
      <dc:date>2021-03-10T23:28:24Z</dc:date>
    </item>
  </channel>
</rss>

