<?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: Dopbox token validity in Discuss Dropbox Developer &amp; API</title>
    <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Dopbox-token-validity/m-p/668549#M3269</link>
    <description>&lt;P&gt;While the option for creating new long-lived access tokens is no longer available, we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s) without interruption, if you have any, but you won't be able to create more.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can find &lt;A href="https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#updating-access-token-type" target="_blank" rel="noopener noreferrer"&gt;more information on this migration here&lt;/A&gt;. Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. You can find more information in the &lt;A href="https://developers.dropbox.com/oauth-guide" target="_blank" rel="noopener noreferrer"&gt;OAuth Guide&lt;/A&gt; and &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#authorization" target="_blank" rel="noopener noreferrer"&gt;authorization documentation&lt;/A&gt;. There's a basic outline of processing this flow in &lt;A href="https://dropbox.tech/developers/using-oauth-2-0-with-offline-access" target="_blank" rel="noopener noreferrer"&gt;this blog post&lt;/A&gt; which may serve as a useful example. If you will ever need to get new long-term authorizations, you would need to update to use this functionality instead.&lt;/P&gt;</description>
    <pubDate>Thu, 16 Mar 2023 13:28:22 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2023-03-16T13:28:22Z</dc:date>
    <item>
      <title>Dopbox token validity</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Dopbox-token-validity/m-p/668447#M3268</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;We have a web application where user can load files, and this are then loaded to dropbox&lt;BR /&gt;To access my Dropbox account, I have a non-expiring token, so far everything is working fine but I saw in your documentation that you are no longer offering these non-expiring tokens.&lt;BR /&gt;So, my question is, should I change something in my side? will the current non expiring token continue working?&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 19:45:19 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Dopbox-token-validity/m-p/668447#M3268</guid>
      <dc:creator>ALGOS</dc:creator>
      <dc:date>2023-03-16T19:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: Dopbox token validity</title>
      <link>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Dopbox-token-validity/m-p/668549#M3269</link>
      <description>&lt;P&gt;While the option for creating new long-lived access tokens is no longer available, we don't currently have a plan to disable existing long-lived access tokens. (If that changes, we will of course announce that ahead of time.) That being the case, you can continue using existing long-lived access token(s) without interruption, if you have any, but you won't be able to create more.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can find &lt;A href="https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens#updating-access-token-type" target="_blank" rel="noopener noreferrer"&gt;more information on this migration here&lt;/A&gt;. Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. You can find more information in the &lt;A href="https://developers.dropbox.com/oauth-guide" target="_blank" rel="noopener noreferrer"&gt;OAuth Guide&lt;/A&gt; and &lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#authorization" target="_blank" rel="noopener noreferrer"&gt;authorization documentation&lt;/A&gt;. There's a basic outline of processing this flow in &lt;A href="https://dropbox.tech/developers/using-oauth-2-0-with-offline-access" target="_blank" rel="noopener noreferrer"&gt;this blog post&lt;/A&gt; which may serve as a useful example. If you will ever need to get new long-term authorizations, you would need to update to use this functionality instead.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 13:28:22 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Discuss-Dropbox-Developer-API/Dopbox-token-validity/m-p/668549#M3269</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2023-03-16T13:28:22Z</dc:date>
    </item>
  </channel>
</rss>

