feat: SubscriptionController: trigger token refresh #6374
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthiasgeihs
force-pushed
the
mg/subscription-controller/refetch-token
branch
from
d1da73f to
769b77c
Compare
matthiasgeihs
changed the base branch from
main
to
feat/shield-subscription-controller
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
matthiasgeihs
force-pushed
the
mg/subscription-controller/refetch-token
branch
from
4b2e43e to
7640869
Compare
matthiasgeihs
force-pushed
the
mg/subscription-controller/refetch-token
branch
from
7640869 to
7e994de
Compare
If we perform a sign out on the authentication controller, then the next access token request will trigger fetch a fresh token.
matthiasgeihs
force-pushed
the
mg/subscription-controller/refetch-token
branch
from
7e994de to
b6c58e9
Compare
tuna1207
approved these changes
Sep 9, 2025
GuillaumeRx
pushed a commit
that referenced
this pull request
Sep 9, 2025
Add a "triggerAuthTokenRefresh" method to the SubscriptionController, which allows to trigger a refresh of the access token, for example, after the subscription status has changed. <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs), highlighting breaking changes as necessary - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explanation
Add a "triggerAuthTokenRefresh" method to the SubscriptionController, which allows to trigger a refresh of the access token, for example, after the subscription status has changed.
References
Checklist