-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fout 400: invalid_request - urn:ietf:wg:oauth:2.0:oob #112
Comments
I have the same problem right now. And I do not know how to fix it. If you decide to explain yourself, please. |
Can't solve it. I tried by changing REDIRECT_URI from the authorize.py file but didn't make it work. This one is still working if you need: https://github.com/zume2020/Telegram-bot-Google-Drive Since telegram only allow up to 20 MB per file to upload, I think none of both bots are what I need. |
Yes, I also tried to change something there, but nothing worked for me either. My friend said that the problem there is in redirection. Thanks for the link to the second bot. If I find a solution to the problem (Or if a friend helps me fix this error) then I will write how to fix it. |
there is the reason. google think the oauth method (oob) is unsafe. so it close the support .the bot must use the new oauth method. https://developers.google.com/identity/protocols/oauth2/resources/oob-migration |
Who has been able to bypass the OOB block and set up authentication? Please, help. I really need this bot! |
That zume2020 is not asking for client IDs and secrets and it's not getting deployed |
|
Hello. i'm getting this error when trying to give access to my drive account.
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow Migration Guide linked in the developer docs below to migrate your app to an alternative method.
Details van verzoek: redirect_uri=urn:ietf:wg:oauth:2.0:oob
Is this bot still working?
The text was updated successfully, but these errors were encountered: