Headless Google Social Auth #4046
Replies: 1 comment 1 reply
-
I realise I can solve the problem by just using the headless provider token endpoint. all is good, closing this. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Does anyone knows how can I edit the redirect_uri from the oauth redirect?
Right now my django settings look like this,
and I am calling the headless Provider redirect which works but doing the auth flow, the redirect uri is wrong but I dont know where to set it in the DB
I cant get the redirect_uri to point to https://backend-10-4-73-61.nip.io/accounts/google/login/callback/
Right now it is pointing to http://10.4.73.61:9001/accounts/google/login/callback/
I am hosting both the backend and frontend under nip.io to try out google social auth, with self signed cert, using nginx.
https://web-10-4-73-61.nip.io/
https://backend-10-4-73-61.nip.io/
Do let me know if more information is needed. Thanks!
This is the allauth react example for reference of the same log in.
Beta Was this translation helpful? Give feedback.
All reactions