I have been using the internal browser to authenticate Dropbox with both OAUTH1 and OAUTH2 (APIV2). Lately I am getting the issue where, after entering the email address and password, the Sign In button is greyed out. This happens now on ALL systems (3x VMs 2x hard systems). All were previously working.
Have you tried setting ExternalBrowser = true? Dropbox always insisted (and will only approve) applications that use the user default browser.
No One has had this defect - see Greyed Sign In button?
Bruno,
Bruno,
We are seeing this using an embedded WebBrowser control in a WPF application and an MFC application. This is on Windows 10, Internet Explorer 11.64.16299.0. The same applications worked just fine up until very recently. Using the same URL in IE directly instead of in the browser control works fine.
I know that using an embedded browser is no longer the recommended way to do the Dropbox oauth but making that change our applications will take some time and we need a solution for our users as soon as possible. We have a number of users of our software who are now unable to connect our application to Dropbox. Would appreciate any help.
POST 2
@cspro It looks like, unfortunately, the browser control will effectively use an older browser engine (e.g., effectively IE 9), even when a newer browser is installed (e.g., IE 11), as evidenced by it working in the system browser on the same device.
We are looking into it to see if there's something we can do, but since these older browsers are technically unsupported, I can't make any promises.
POST 3
Thanks @Greg K. for the quick reply. Your answer got me to a workaround.
I didnt realize that the WebBrowser control could use an older version of IE even with a newer one installed. When I looked into that I found that in fact that the browser does use the installed version of IE but runs it in emulation mode. It pretends to be an older version. However you can change that behavior by setting the registry key
HKLM\Software\Microsoft<wbr>Internet Explorer\Main\FeatureControl<wbr>FEATURE_BROWSER_EMULATION<name of your application.exe> to 0x2af9.
This makes it emulate IE11 instead of IE9. I made this change on my machine and the sign in button is now enabled.
From what I read online, you could fix this on your end as well by adding the following to the header:
<meta http-equiv="X-UA-Compatible" content="IE=11">
I have not tested that.
More details here:
https://stackoverflow.com/questions/23776951/set-wpf-webbrowser-control-to-use-ie10-mode
POST 4
Thanks for the information! We'll look into it.
Hi,
As suggested in the posts you mentioned, you can check the configuration in the registry and add/change it manually if required.