<?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 OAuth: Access token per infrastrucure or access token per client? in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-Access-token-per-infrastrucure-or-access-token-per-client/m-p/242198#M13502</link>
    <description>&lt;P&gt;We have two elements (clients) in our infrastructure:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;First Client: A service that receives webhooks. Each time a webhook is received it tries to get information from dropbox.&lt;/LI&gt;&lt;LI&gt;Second Client: A user interface(.net) that allows to download files from dropbox.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Both services are accessing to dropbox.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Should we ask for an access token for each client or we can use only one for both.&lt;/P&gt;&lt;P&gt;It's important for us that you figure out that we want both clients are like a single infrastructure. We are trying to avoid that a user is requested for "the same" infrastructure twice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're considering that both clients as a single "client" even thought both are running in separated behaviors. So, what about if both clients are using the same access token?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope I've explained so well.&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:19:15 GMT</pubDate>
    <dc:creator>living-jordi</dc:creator>
    <dc:date>2019-05-29T09:19:15Z</dc:date>
    <item>
      <title>OAuth: Access token per infrastrucure or access token per client?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-Access-token-per-infrastrucure-or-access-token-per-client/m-p/242198#M13502</link>
      <description>&lt;P&gt;We have two elements (clients) in our infrastructure:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;First Client: A service that receives webhooks. Each time a webhook is received it tries to get information from dropbox.&lt;/LI&gt;&lt;LI&gt;Second Client: A user interface(.net) that allows to download files from dropbox.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Both services are accessing to dropbox.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Should we ask for an access token for each client or we can use only one for both.&lt;/P&gt;&lt;P&gt;It's important for us that you figure out that we want both clients are like a single infrastructure. We are trying to avoid that a user is requested for "the same" infrastructure twice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're considering that both clients as a single "client" even thought both are running in separated behaviors. So, what about if both clients are using the same access token?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope I've explained so well.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:19:15 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-Access-token-per-infrastrucure-or-access-token-per-client/m-p/242198#M13502</guid>
      <dc:creator>living-jordi</dc:creator>
      <dc:date>2019-05-29T09:19:15Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth: Access token per infrastrucure or access token per client?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-Access-token-per-infrastrucure-or-access-token-per-client/m-p/242289#M13509</link>
      <description>Either way would work, but for the sake of simplicity you may want to use a single access token for both clients.</description>
      <pubDate>Tue, 19 Sep 2017 17:47:19 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth-Access-token-per-infrastrucure-or-access-token-per-client/m-p/242289#M13509</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-09-19T17:47:19Z</dc:date>
    </item>
  </channel>
</rss>

