You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
can't retrieve token from django-oauth-toolkit (Error 405) - Though when sending the exact same request call manually (from within docker) it is succesful.
#49
Open
jannefleischer opened this issue
Mar 20, 2024
· 3 comments
I am really not sure if this is an issue with taig-contrib-openid-auth or with the django-oauth-tollkit or with my setup, so any input would be helpful:
I am trying to connect my taiga deployment (in docker environment behind a apache-reverse-proxy) with our geonode as the oauth-provider (which uses the django-oauth-toolkit internally). Other services like a wordpress installation and our gitlab-ce instance are fine using the geonode for exact that porpose.
Every time when I push the Sign-in-with-geonode-button, it makes the above post request, I gets a 405-Error back.
If I run the exact same code from within my taiga-back docker container (and even from taiga-gateway after installing python there) the token is returned by the endpoint totally fine. The only difference I make is to prolong the expiry date on the used grant code manually, due to a very fast expiration and slow fingers.
The only feedback from geonode/django-oauth-toolkit is this line in logs - so at least it arrives there: [20/Mar/2024:09:47:57 +0000] "GET /o/token/ HTTP/1.1" 405 0 "-" "python-requests/2.27.1"
So I am really, really not sure whats happening here. Maybe something related to the apache2-reverse-proxy, but I am not shure, but doesn't seem like that, as the request arrives there fine.
Any idea what to check next?
The text was updated successfully, but these errors were encountered:
jannefleischer
changed the title
can't retrieve token from django-oauth-toolkit (Error 405) - Though when sending the exact same request call manually it is succesful.
can't retrieve token from django-oauth-toolkit (Error 405) - Though when sending the exact same request call manually (from within docker) it is succesful.
Mar 20, 2024
Hi,
I am really not sure if this is an issue with taig-contrib-openid-auth or with the django-oauth-tollkit or with my setup, so any input would be helpful:
I am trying to connect my taiga deployment (in docker environment behind a apache-reverse-proxy) with our geonode as the oauth-provider (which uses the django-oauth-toolkit internally). Other services like a wordpress installation and our gitlab-ce instance are fine using the geonode for exact that porpose.
The issue is here:
taiga-contrib-openid-auth/back/taiga_contrib_openid_auth/connector.py
Line 92 in 7f6b03a
taiga-contrib-openid-auth/back/taiga_contrib_openid_auth/connector.py
Line 121 in 7f6b03a
Every time when I push the Sign-in-with-geonode-button, it makes the above post request, I gets a 405-Error back.
If I run the exact same code from within my taiga-back docker container (and even from taiga-gateway after installing python there) the token is returned by the endpoint totally fine. The only difference I make is to prolong the expiry date on the used grant code manually, due to a very fast expiration and slow fingers.
The only feedback from geonode/django-oauth-toolkit is this line in logs - so at least it arrives there:
[20/Mar/2024:09:47:57 +0000] "GET /o/token/ HTTP/1.1" 405 0 "-" "python-requests/2.27.1"
So I am really, really not sure whats happening here. Maybe something related to the apache2-reverse-proxy, but I am not shure, but doesn't seem like that, as the request arrives there fine.
Any idea what to check next?
The text was updated successfully, but these errors were encountered: