<?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: Server-side application with NO way to use the standard OAuth flow in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/512892#M25222</link>
    <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1431790"&gt;@RosenPetrov&lt;/a&gt; The examples you linked to are the current samples for implementing the OAuth app flow with the Dropbox .NET SDK. Are they not working for you, or can you clarify what you're stuck on?&lt;/P&gt;</description>
    <pubDate>Mon, 12 Apr 2021 15:20:13 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2021-04-12T15:20:13Z</dc:date>
    <item>
      <title>Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/495415#M24708</link>
      <description>&lt;P&gt;One of our server-side applications should be able to access all of our Dropbox Business files. &lt;FONT color="#808080"&gt;This application is exclusively meant for use by our own organization, for&amp;nbsp;background file handling, meaning that we are &lt;STRONG&gt;&lt;I&gt;not&lt;/I&gt;&lt;/STRONG&gt;&amp;nbsp;planning to ever&amp;nbsp;"Apply for production" &lt;EM&gt;(= open up to external users)&lt;/EM&gt; this app through Dropbox's App console.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now we're using a&amp;nbsp;Generated access token (No expiration).&lt;/P&gt;&lt;P&gt;And we pass that &lt;STRONG&gt;long-lived&lt;/STRONG&gt; token to the &lt;EM&gt;DropboxClient&lt;/EM&gt; constructor that's in the&amp;nbsp;&lt;A title=".NET SDK for API v2" href="https://www.dropbox.com/developers/documentation/dotnet" target="_blank" rel="noopener"&gt;Dropbox SDK for .NET&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;PRE&gt;using&amp;nbsp;(var&amp;nbsp;client&amp;nbsp;=&amp;nbsp;new&amp;nbsp;DropboxClient(&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;oauth2Token&lt;/STRONG&gt;&lt;/FONT&gt;))
{
  // Perform actions here
}&lt;/PRE&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I've read that&amp;nbsp;long-lived tokens are deprecated, although there are no concrete plans yet(?) to actually disable them.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Still I'd like to know: can we switch to a&amp;nbsp;&lt;STRONG&gt;short-lived&lt;/STRONG&gt; token today?&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Which we also generate through the App console and pass to the&amp;nbsp;DropboxClient in the same way. But now also get a Refresh Token that's needed to replace the short-lived token, as soon as it expires. All without involving a user (&lt;EM&gt;i.e. have no interactive OAuth flow at all&lt;/EM&gt;).&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Or should we simply not worry about this until the long-lived tokens are actually announced to be disabled by the Dropbox team?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;Richard&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 Feb 2021 07:30:29 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/495415#M24708</guid>
      <dc:creator>Agrometius_Smart_Farming</dc:creator>
      <dc:date>2021-02-11T07:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/495517#M24713</link>
      <description>&lt;P&gt;Applying for production is only required if your application&amp;nbsp;intends to link more than 50 users.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your application may use refresh tokens to retrieve new access tokens without needing to apply for production access. Refresh tokens do not expire; you may pass them to the SDK which will then automatically retrieve new access tokens as required. You can switch to this methodology now.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You will need to complete an OAuth to retrieve a refresh token; they are not returned in the 'generate access token' section of the developer console.&amp;nbsp; This OAuth will only be required once (per account) to retrieve a refresh token.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 21:16:56 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/495517#M24713</guid>
      <dc:creator>kylea</dc:creator>
      <dc:date>2021-02-10T21:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/512860#M25219</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you elaborate a bit more on how to refactor the code to accomplish what you said? I am looking into the examples &lt;A href="https://github.com/dropbox/dropbox-sdk-dotnet/tree/main/dropbox-sdk-dotnet/Examples" target="_blank"&gt;https://github.com/dropbox/dropbox-sdk-dotnet/tree/main/dropbox-sdk-dotnet/Examples&lt;/A&gt; but seems that they actually include more things that this needs like some redirect URLs, JS handling, etc. Which example could I follow?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 13:10:58 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/512860#M25219</guid>
      <dc:creator>RosenPetrov</dc:creator>
      <dc:date>2021-04-12T13:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/512892#M25222</link>
      <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1431790"&gt;@RosenPetrov&lt;/a&gt; The examples you linked to are the current samples for implementing the OAuth app flow with the Dropbox .NET SDK. Are they not working for you, or can you clarify what you're stuck on?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 15:20:13 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/512892#M25222</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2021-04-12T15:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/513064#M25226</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am looking into the 'SimpleTest' and I see these&amp;nbsp;LoopbackHost, RedirectUri and&amp;nbsp;JSRedirectUri but in my case I need this Authentication to happen in a background without user interaction. Could you point me in the right direction how I could accomplish that. Maybe some high level steps but not code would be enough.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks &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;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 06:49:19 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/513064#M25226</guid>
      <dc:creator>Rosen Petrov</dc:creator>
      <dc:date>2021-04-13T06:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: Server-side application with NO way to use the standard OAuth flow</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/513181#M25227</link>
      <description>&lt;P&gt;&lt;a href="https://www.dropboxforum.com/t5/user/viewprofilepage/user-id/1432062"&gt;@Rosen Petrov&lt;/a&gt; It is not possible to get authorization to access an account purely via a background process. Authorizing an app requires manual user interaction the first time, for the user to indicate to Dropbox that they want to allow the app to access their account. After that though, the app can store and re-use the resulting access token and optional refresh token to make further API calls without further manual user interaction. I recommend reading &lt;A href="https://developers.dropbox.com/oauth-guide" target="_self"&gt;the OAuth Guide&lt;/A&gt; for more information on how this process works at a high level.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 14:14:34 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Server-side-application-with-NO-way-to-use-the-standard-OAuth/m-p/513181#M25227</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2021-04-13T14:14:34Z</dc:date>
    </item>
  </channel>
</rss>

