<?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: OAuth 2.0 Access Token Validity in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46536#M1452</link>
    <description>&lt;P&gt;Because Dropbox does a database lookup for each request, our bearer tokens are immediately revocable by code or by the user (via &lt;A href="https://www.dropbox.com/account/security" rel="nofollow noreferrer"&gt;https://www.dropbox.com/account/security&lt;/A&gt;). We reviewed our OAuth 2 implementation with respect to the issues raised in that Stack Overflow answer as well as many other sources, and we're comfortable with what we have from a security perspective.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Feb 2015 10:00:37 GMT</pubDate>
    <dc:creator>Steve M.</dc:creator>
    <dc:date>2015-02-24T10:00:37Z</dc:date>
    <item>
      <title>OAuth 2.0 Access Token Validity</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46533#M1449</link>
      <description>&lt;P&gt;I have been trying to use the dropbox apis through OAuth 2.0 authentication support. I found that the access token generated through the authorize and token end points seems to be valid for over 2 days. I had expected it to expire after a while (say couple of hours) assuming that to be a standard.&lt;/P&gt;

&lt;P&gt;I would like to know the validity period of the access token. Can someone share provide some inputs? &lt;BR /&gt;
Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:44:57 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46533#M1449</guid>
      <dc:creator>Amit1</dc:creator>
      <dc:date>2019-05-29T09:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth 2.0 Access Token Validity</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46534#M1450</link>
      <description>&lt;P&gt;See &lt;A href="https://www.dropbox.com/developers/support#token-expiration" rel="nofollow noreferrer"&gt;https://www.dropbox.com/developers/support#token-expiration&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;Access tokens effectively don't expire.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Feb 2015 14:09:29 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46534#M1450</guid>
      <dc:creator>Steve M.</dc:creator>
      <dc:date>2015-02-23T14:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth 2.0 Access Token Validity</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46535#M1451</link>
      <description>&lt;P&gt;Isn't it a security issue if the token don't expire? &lt;A href="http://stackoverflow.com/a/7035926/537503" rel="nofollow noreferrer"&gt;http://stackoverflow.com/a/7035926/537503&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Feb 2015 18:21:33 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46535#M1451</guid>
      <dc:creator>Amit1</dc:creator>
      <dc:date>2015-02-23T18:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth 2.0 Access Token Validity</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46536#M1452</link>
      <description>&lt;P&gt;Because Dropbox does a database lookup for each request, our bearer tokens are immediately revocable by code or by the user (via &lt;A href="https://www.dropbox.com/account/security" rel="nofollow noreferrer"&gt;https://www.dropbox.com/account/security&lt;/A&gt;). We reviewed our OAuth 2 implementation with respect to the issues raised in that Stack Overflow answer as well as many other sources, and we're comfortable with what we have from a security perspective.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2015 10:00:37 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46536#M1452</guid>
      <dc:creator>Steve M.</dc:creator>
      <dc:date>2015-02-24T10:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth 2.0 Access Token Validity</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46537#M1453</link>
      <description>&lt;P&gt;&lt;img class="lia-deferred-image lia-image-emoji" src="https://www.dropboxforum.com/html/@FBF7D2AB59A0D6E861EBF6A36F93B7E2/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2015 13:16:17 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-2-0-Access-Token-Validity/m-p/46537#M1453</guid>
      <dc:creator>Amit1</dc:creator>
      <dc:date>2015-02-24T13:16:17Z</dc:date>
    </item>
  </channel>
</rss>

