feat: add loginWithCustomTokenExchange and deprecate exchangeToken #1010
+197
−27
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.
Changes
This PR aligns with the auth0-spa-js v2.14.0 release and introduces the
loginWithCustomTokenExchangemethod as the recommended way to perform custom token exchange.What's Changed
loginWithCustomTokenExchange()method toAuth0ContextandAuth0ProviderexchangeToken()method with clear migration guidance@auth0/auth0-spa-jsdependency to^2.14.0EXAMPLES.mdwith new method usageMigration Guide
The
exchangeTokenmethod is now deprecated. Please migrate tologinWithCustomTokenExchange:Backward Compatibility
The
exchangeTokenmethod is maintained for backward compatibility and internally delegates tologinWithCustomTokenExchange. It will be removed in the next major version.Testing
References