Open arnarl opened 10 years ago
Hi,
Even I'm facing same problem. Changed endpoints as given in link. I ran into another problem - "The provided value for the input parameter 'redirect_uri' is not valid. The expected value is 'https://login.live.com/oauth20_desktop.srf' or a URL which matches the redirect URI registered for this client application".
Did you do any other changes in your code to make it work? Thanks in advance.
Not that I can remember. Sorry. It's the only change in our fork as well.
I did see similar error messages before this patch but didn't track them down. (We have a web application in case the _desktop stuff is relevant.)
We've packaged a custom velruse distribution that our app downloads every time it runs setup.py. I could send you that one to try/diff in case I messed something up in the patch and also fixed something else that I forgot to commit. I won't be able to do that myself for a few days.
Thanks for the reply. I was able to fix it, there was a problem with my registered redirect-uri which wasn't under my control. Sorry, that I bothered you. Hoping that this fix will not affect us in any other way..:)
BTW, I'm thinking down the same line to create custom velruse dist..
We've had a problems with the live.com provider intermittently failing. Today it started failing all the time returning the error message 'The HTTP request was forbidden with client authentication scheme "Anonymous"'.
According to http://social.msdn.microsoft.com/Forums/onedrive/en-US/577aa2de-9409-405a-835f-327e06965f52/oauth-service-down?forum=messengerconnect — which may not be the most authoritative source — there are new endpoints that should be used.
The patch simply uses these new endpoints and our problems went away.