<?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: Dropbox integration with other applications in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-integration-with-other-applications/m-p/257941#M14961</link>
    <description>As a security feature, OAuth 2 redirect URIs must be pre-registered exactly. Wildcards and dynamic registration are not supported.&lt;BR /&gt;&lt;BR /&gt;One thing you may be able to do instead is to use one static redirect URI but encode the necessary information in the 'state' parameter, and decode it as necessary after the redirect back to your app, to handle it as necessary:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize" target="_blank"&gt;https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Alternatively, you could forgo using a redirect URI entirely. With the "code" flow, you can omit redirect_uri and have the user copy and paste the code manually.</description>
    <pubDate>Wed, 27 Dec 2017 15:05:53 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2017-12-27T15:05:53Z</dc:date>
    <item>
      <title>Dropbox integration with other applications</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-integration-with-other-applications/m-p/257902#M14956</link>
      <description>&lt;P&gt;Hey, We have developed an on-premises application and have integrated dropbox older version. Now since dropbox has upgraded its API we have no other option than to migrate from v1 to v2. But the problem in v2 is that we require dynamic redirect uri options. That is we will have different redirect uri for different users. But v2 compels us to store the redirect uri before hand in the dropbox account which is not possible in our case. Hope you understand our problem and provide us with a better solution.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:16:29 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-integration-with-other-applications/m-p/257902#M14956</guid>
      <dc:creator>Kishore4</dc:creator>
      <dc:date>2019-05-29T09:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: Dropbox integration with other applications</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-integration-with-other-applications/m-p/257941#M14961</link>
      <description>As a security feature, OAuth 2 redirect URIs must be pre-registered exactly. Wildcards and dynamic registration are not supported.&lt;BR /&gt;&lt;BR /&gt;One thing you may be able to do instead is to use one static redirect URI but encode the necessary information in the 'state' parameter, and decode it as necessary after the redirect back to your app, to handle it as necessary:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize" target="_blank"&gt;https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Alternatively, you could forgo using a redirect URI entirely. With the "code" flow, you can omit redirect_uri and have the user copy and paste the code manually.</description>
      <pubDate>Wed, 27 Dec 2017 15:05:53 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Dropbox-integration-with-other-applications/m-p/257941#M14961</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-12-27T15:05:53Z</dc:date>
    </item>
  </channel>
</rss>

