-
Notifications
You must be signed in to change notification settings - Fork 105
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
Google OAuth 2.0 failing with Error 400: invalid_request #284
Comments
What do the error details say? |
Same here: Fehler 400: invalid_request The oauth2 libraray uses the out of band mechanism which is no longer supported by google. I tried to fix that but it seems that you need to use a google sdk for that now. Maybe someone knows more about that? |
It seems that there is a fix: kidd/org-gcal.el#191 . It is basically they switchend from oauth2 to oauth2-auto |
Looks like @MartinNowak is working on getting oauth2-auto into MELPA, in this comment he says it is with org-caldav in mind: telotortium/emacs-oauth2-auto#3 (comment) @MartinNowak have you started working on modifying org-caldav to use oauth2-auto? I am not currently using org-caldav with Google, so any help is appreciated. |
Link to duplicate version of this issue: |
Does this mean it should work again? In this case, is there more information about how to use it? |
Yes, it's working like a charm :) Just follow the instructions. Make sure you enable both Calendar and Caldav APIs. If you need more help don't hesitate to ask me. |
Oh, I think I know my issue. Could you just give a short hint how to switch from oauth2 to oauth2-auto ? |
Definitely! Please go here and follow the installation instructions. They should be the exact same whether you use org-gcal or org-caldav. https://github.com/emacsmirror/org-gcal?tab=readme-ov-file#installation Please do not hesitate to ask again if you have any concerns or questions. Abe |
If i remove the oauth2 package org-caldav says oauth2 is missing, but the oauth2-auto is installed. If i install the oauth2 package again, i get the Error 400 again. For me it looks like org-caldav has to do changes to use oauth2-auto instead of oauth2. I don't figure out how you did it. |
After all I could fetch my google events with org-gcal, but I don't get it working with org-caldav. Can you help me with that? |
Can you please share your config in your init file. Possibly share a screenshot of the error you are facing. |
I'm not sure why @AbeEtan says it's fixed. It's not. The oauth2-auto package has recently been added to MELPA, which uses the new oauth flow. However, it hasn't been integrated with this repository yet. We still need a PR for Google to work again. |
Thanks, @boogsbunny, thats exactly what i thought. |
I am able to sync with my google calendar and bidirectional as well. No issues what so ever. |
@AbeEtan Are you sure you are using Or is there a way to authenticate with I also got it working with |
I apologize for the miscommunication. I am using That being said, When re-authenticate, I get a warning message |
I have a working solution but can't make a PR for it because my code is a mess and likely inefficient as it doesn't handle caching the credentials or anything like that. It's modeled after the org-gcal solution. I'm posting it here in case it can help others and (hopefully) speed along the "real" fix. The solution requires
|
Hello lovely people!
I have done everything right, but I am getting this error. Any idea on how to fix this error?
Thank you!
The text was updated successfully, but these errors were encountered: