Google OAuth - http redirect issue - ODOO 18.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- authentication, infrastructure
Research direction
Start by comparing the redirect_uri shown in the Google error with the OAuth redirect URI registered in Google Cloud Console, then review the HTTP-to-HTTPS reverse-proxy behavior for /google_gmail/confirm. Done means the generated redirect uses the correct HTTPS URL and the Gmail connection completes without the 400 mismatch or forbidden response.
Written by the indexing model from the issue text.
Description
It seems that clicking on Connect your Gmail accout in odoo fails because of a 400: redirect_uri_mismatch error.
I have attempted everything in the documents however something isn't lining up and I do not believe it is my configuration.
HTTP > HTTPS redirect is working correctly on my site/server through my reverse proxy
reply from Google:
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy.
If you're the app developer, register the redirect URI in the Google Cloud Console.
Request details: redirect_uri=http://myhostnamehere.com/google_gmail/confirm flowName=GeneralOAuthFlow
[Related developer documentation](https://developers.google.com/identity/protocols/oauth2/web-server#authorization-errors-redirect-uri-mismatch)
If I try to visit: http://myhostnamehere.com/google_gmail/confirm
I do get the FORBIDDEN error message - however I have updated the google plug in as described in the documentation and that hasn't fixed it. This is also a new installation so I would assume the latest plug in would have been installed.
Forbidden
You don't have the permission to access the requested resource. It is either read-protected or not readable by the server.
I am stuck unfortuantely at this point to understand how to move forward.
- Dominant language
- Dockerfile
- Stars
- 1.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from odoo/docker
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
Missing PyJWT ?Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 79/100
gregwebs/agent-vm-images#216 ·
Maintainers usually reply within 1 day
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenPrinting/cups#1826 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mongodb/kingfisher#588 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linuxhsj/openclaw-zero-token#302 ·