<?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: OAuth2 Flow in Chrome App fails in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343114#M19809</link>
    <description>&lt;P&gt;First, for reference, are you using &lt;A href="https://github.com/dropbox/dropbox-sdk-js" target="_self"&gt;the official&amp;nbsp;Dropbox API v2 JavaScript SDK&lt;/A&gt;?&lt;/P&gt;
&lt;P&gt;Looking at the two URLs you shared, the differences appear to be: (unless something got lost in formatting when posting to the forum)&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;the URL parameter order&lt;/LI&gt;
&lt;LI&gt;the URL parameter encoding&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Can you try initially supplying the URL exactly as it is the second, reformatted version? I believe it's technically wrong to supply it like that since the 'redirect_uri' URL parameter isn't properly URL encoded, but it may be useful for the sake of troubleshooting to see if that helps.&lt;/P&gt;</description>
    <pubDate>Mon, 06 May 2019 16:58:07 GMT</pubDate>
    <dc:creator>Greg-DB</dc:creator>
    <dc:date>2019-05-06T16:58:07Z</dc:date>
    <item>
      <title>OAuth2 Flow in Chrome App fails</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343002#M19800</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm working on a ChromeOS App that integrates with Dropbox. I can't get the OAuth2 token flow to work using chrome.identity.launchWebAuthFlow. Rolling my own version of that API to do the token flow works.&lt;/P&gt;&lt;P&gt;The most suspicious thing I see in the browser logs is that there is a GET to /oauth2/authorize that gets aborted. First there is a GET to &lt;SPAN&gt;ttps://&lt;A href="http://www.dropbox.com/oauth2/authorize?client_id=redacted&amp;amp;force_reapprove=true&amp;amp;redirect_uri=https%3A%2F%2Fwww.dropbox.com%2F1%2Foauth2%2Fdisplay_token&amp;amp;response_type=token" target="_blank"&gt;www.dropbox.com/oauth2/authorize?client_id=redacted&amp;amp;force_reapprove=true&amp;amp;redirect_uri=https%3A%2F%2Fwww.dropbox.com%2F1%2Foauth2%2Fdisplay_token&amp;amp;response_type=token&lt;/A&gt;, then a GET to&amp;nbsp;&lt;A href="https://www.dropbox.com/oauth2/authorize?client_id=redacted&amp;amp;response_type=token&amp;amp;redirect_uri=https://www.dropbox.com/1/oauth2/display_token&amp;amp;force_reapprove=true,&amp;nbsp;" target="_blank"&gt;https://www.dropbox.com/oauth2/authorize?client_id=redacted&amp;amp;response_type=token&amp;amp;redirect_uri=https://www.dropbox.com/1/oauth2/display_token&amp;amp;force_reapprove=true,&amp;nbsp;&lt;/A&gt;&lt;/SPAN&gt;that gets aborted and immediately reissued. My hypothesis is that when that request is aborted, the launchWebAuthFlow API assumes that the login process has failed and gives up.&lt;/P&gt;&lt;P&gt;Additional information about my use case:&lt;BR /&gt;* I have 2-factor authentication, using Google Authenticator, configured for my account&lt;/P&gt;&lt;P&gt;Any thoughts or advice would be appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:06:40 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343002#M19800</guid>
      <dc:creator>kp8080</dc:creator>
      <dc:date>2019-05-29T09:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth2 Flow in Chrome App fails</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343114#M19809</link>
      <description>&lt;P&gt;First, for reference, are you using &lt;A href="https://github.com/dropbox/dropbox-sdk-js" target="_self"&gt;the official&amp;nbsp;Dropbox API v2 JavaScript SDK&lt;/A&gt;?&lt;/P&gt;
&lt;P&gt;Looking at the two URLs you shared, the differences appear to be: (unless something got lost in formatting when posting to the forum)&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;the URL parameter order&lt;/LI&gt;
&lt;LI&gt;the URL parameter encoding&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Can you try initially supplying the URL exactly as it is the second, reformatted version? I believe it's technically wrong to supply it like that since the 'redirect_uri' URL parameter isn't properly URL encoded, but it may be useful for the sake of troubleshooting to see if that helps.&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 16:58:07 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343114#M19809</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2019-05-06T16:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth2 Flow in Chrome App fails</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343897#M19864</link>
      <description>&lt;P&gt;I tried using the official SDK to get the login URL. Same symptoms.&amp;nbsp; When I have some time I'll see if I can try the reformatted URL.&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2019 15:19:32 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/OAuth2-Flow-in-Chrome-App-fails/m-p/343897#M19864</guid>
      <dc:creator>kp8080</dc:creator>
      <dc:date>2019-05-10T15:19:32Z</dc:date>
    </item>
  </channel>
</rss>

