-
-
Notifications
You must be signed in to change notification settings - Fork 616
Support refresh tokens #2141
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
Comments
I'm not generally a TypeScript developer so my JS skills are... lacking but it looks as though this could be supported in a way by creating a middleware-d Lines 59 to 92 in 1643201
I think it would be nice to have first-class support for refresh tokens in the SDK itself, but it seems as though telling the SDK to not bother with access tokens, and then handling them in the request function, could be an approach. (Or at least prove a POC.) |
Related to #801 - |
Rewriting the SDK's |
Functions added in #2178 |
Is your feature request related to a problem? Please describe.
Refresh tokens were introduced in MSC2918 but do not appear to be supported in the JS SDK.
Describe the solution you'd like
Support for refresh tokens and automatic refresh based on known expiration or auth failure using expired token.
Describe alternatives you've considered
This is a spec support feature so I do not believe there is an alternative.
Additional context
In more traditional OAuth world, it's possible to use a middleware (such as https://github.com/badgateway/fetch-mw-oauth2) for HTTP transport, but I don't think that would be an option here.
The text was updated successfully, but these errors were encountered: