-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
oauth2/token issue #1484
Comments
Thank you for creating an issue in this repository. Unfortunately, your issue does not comply with community guidelines by not using one of the provided issue templates. Those templates help us better understand your issue and reduce latency as well as communication overhead. Please update your issue in accordance with the issue template that fits best or this issue will be auto-closed in a 3 days. |
Please format the issue (how to format code blocks) and include hydra server logs. Also, you're on a very old version of Hydra and I recommend upgrading to the latest one. |
Thank you and I will provide what is asked |
Hydra always emits logs, you don't need to enable that. |
I'm closing this issue because:
Feel free to post any findings here regardless, if you find them. |
name: oauth2/token refresh token issue
about: oauth2/token is returning an error during refresh token
Describe the bug
oauth2/token refresh token issue
oauth2/token to generate a bearer token responds correctly: with bearer token / refresh token
However, calling oauth2/token to refresh a token is giving us an error
Reproducing the bug
Steps to reproduce the behavior:
curl -X POST http://localhost:32769/oauth2/token -d "grant_type=refresh_token&refresh_token=AAAAAzzzzzzzzzzzzxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAAA&redirect_uri=https://ZZZZZZ" -H "x-api-key : ZZZZZZ" -H 'content-type: application/x-www-form-urlencoded' -H 'Authorization: Basic XXXXXXXX' -vv
Server logs
[ec2-user@ip-12-8-9-6 ~]$ curl -X POST http://localhost:32769/oauth2/token -d "grant_type=refresh_token&refresh_token=AAAAAzzzzzzzzzzzzxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAAA&redirect_uri=https://ZZZZZZ" -H "x-api-key : ZZZZZZ" -H 'content-type: application/x-www-form-urlencoded' -H 'Authorization: Basic XXXXXXXX' -vv
Note: Unnecessary use of -X or --request, POST is already inferred.
Trying 127.0.0.1...
TCP_NODELAY set
Connected to localhost (127.0.0.1) port 32769 (#0)
POST /oauth2/token HTTP/1.1
Host: localhost:32769
User-Agent: curl/7.53.1
Accept: /
x-api-key : ZZZZZZ
content-type: application/x-www-form-urlencoded
Authorization: Basic XXXXXXXX
Content-Length: 166
upload completely sent off: 166 out of 166 bytes
Empty reply from server
Connection #0 to host localhost left intact
curl: (52) Empty reply from server
Environment
Additional context
Since we released last year, we are not having any problem.
3 to 4 weeks ago, a client reported this issue and it still persists until now
The text was updated successfully, but these errors were encountered: