-
-
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
Fail to get refresh token with Hydra version 1.5.0-beta.5 #1910
Comments
What does Are you sure that the scope is accepted appropriately? I can not reproduce this with the quickstart demo. It's also important to note that we have a ton of e2e and integration tests that ensure that this flow works correctly, so I'm pretty sure it has to be something else. |
I actually copied the snippet from someone else in the GitHub board. The actual get is this. |
Yes I used to get both access and refresh token from the exact same client before I upgraded the version. I haven't changed codewise anything apart from bumping the Hydra version to 1.5.0-beta.5. Do I have to change anything from client side or consent provider side now? By the way, when I checked the database table |
Please follow the instructions I provide ( |
Sorry I misunderstood your instruction. This is what I got
|
|
Now it works after updating grant-types! I upgraded Hydra version from Thanks a lot for the help. I guess I should close the issue then? |
I am glad you were able to resolve the issue! Yes, that is indeed a big jump (I think 2 years?)! In the future, check out our upgrade guide which includes breaking changes and other important info:� https://github.com/ory/hydra/blob/master/UPGRADE.md Yup, I'll close this one :) |
Describe the bug
Don't get refresh token with Hydra version 1.5.0-beta.5 even though client is registered with
'offline'
and/or'offline_access'
scope and resource owner granted 'offline' scope in authorization code flow.Reproducing the bug
Steps to reproduce the behavior:
for example
GET /oauth2/auth?client_id=localhost_demo_app&redirect_uri=http%3A%2F%2Flocalhost%3A5000%2Fcallback&response_type=code&scope=offline&state=i6qNJyDPDrIbTEucj4Sc%2Bs52OIVjjxtVZ0Ez7s%2FZJ116%2FIeJibtD1A8iii%2B7ozS%2FqNlL5MTGgIwivs2LQBEjOg%3D%3D&nonce=4c01b5637b3979eeaaab1e282e6ac095497c4e45cb70dbb3fb56af45740b448b
(I do it from my client).Server logs
Expected behavior
Client get back both access and refresh token
Environment
Additional context
Client used to get both access and refresh token with older version (for example, 1.0.0-rc14)
The text was updated successfully, but these errors were encountered: