No auth configuration available for refresh token
See original GitHub issueWhen i use the method performActionWithFreshTokens
after the auth flow completion, and after the access_token is expired, I receive:
java.lang.IllegalStateException: No authorization configuration available for refresh request
What could be gone wrong? Parsing the response? I’ve saved the authState json previously, but I don’t see any lastAuthorizationResponse key…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:19
- Comments:6
Top Results From Across the Web
No authorization configuration available for refresh request okta
Inside Okta >> Admin >> Applications >> OIDC application >> General tab, do you have “Refresh Token” selected for “Allowed grant types”?
Read more >Configure Refresh Token Expiration - Auth0
Enter Absolute Lifetime in seconds. The refresh token expires after the specified interval and can no longer be used to get a new...
Read more >Understanding Refresh Tokens - Auth0
While refresh tokens are often long-lived, the authorization server can invalidate them. Some of the reasons a refresh token may no longer be...
Read more >Use Refresh Tokens - Auth0
To learn more about the authentication methods available for the Authentication API, read Authentication ... to configure this snippet with your account.
Read more >Use Refresh Token Rotation - Auth0
The SDK uses the iframe method if you have set useRefreshTokens to true but no Refresh Token is available in the cache. This...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is quite helpful, if you see no refresh-token being provided either the first time tokens are generated or when they are refreshed, make sure to include
offline_access
to your scope This is the way it worked for me.prior to saving your authState json, ensure you have updated the authState with an
authenticationResponse
and also withtokenResponse
after your handler gets new
accessToken
, andidToken
, yourauthState
is automatically updated with those tokens, and there is no need to invokeupdate
method again. Now you need to store it such as done aboveyourStoringFunctionality( authState.jsonSerializeString() )
.I have to say that the documentation is not very extended in how to do this