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
I have configured a client, with the scope "offline_access".
I call the authorize endpoint with this scope, and the response_type set as "code".
I can get a token and a refresh token when calling the token endpoint.
But when I try to refresh the token, with the refresh_token I received, I always get an error saying "Bad refresh token".
I see nothing related to this error in the shibboleth logs.
The call I make to refresh the token is like : curl -X POST -d "client_id=my-client-id&client_secret=my-secret&grant_type=refresh_token&refresh_token=THE_REFRESH_TOKEN_I_RECEIVED&redirect_uri=http%3A%2F%2Flocalhost%2Fcallback" https://my-idp-address/idp/profile/oidc/token
The text was updated successfully, but these errors were encountered:
I have configured a client, with the scope "offline_access".
I call the authorize endpoint with this scope, and the response_type set as "code".
I can get a token and a refresh token when calling the token endpoint.
But when I try to refresh the token, with the refresh_token I received, I always get an error saying "Bad refresh token".
I see nothing related to this error in the shibboleth logs.
The call I make to refresh the token is like : curl -X POST -d "client_id=my-client-id&client_secret=my-secret&grant_type=refresh_token&refresh_token=THE_REFRESH_TOKEN_I_RECEIVED&redirect_uri=http%3A%2F%2Flocalhost%2Fcallback" https://my-idp-address/idp/profile/oidc/token
The text was updated successfully, but these errors were encountered: