Hacky mechanism for preventing token exchange step #110
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
* Changes required for compilation (updated react-native) * If 'skipTokenExchange' is provided in the addlParameterMap and is a boolean 'true' value, do not execute the token exchange process, just return the code, state, and redirect_uri over the bridge * Added the alternate return type for 'authorize' * remove runtime arguments check * test * squash this * squash me * [iOS] Expose option to skip token request
handle errors on skipTokenExchange callback
Contributor
|
Thanks for the PR! I'm working on making this production-ready, I'll merge it when I'm ready to make a PR to change the API to the format we discussed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR (discussed in #96) adds support for a boolean
additionalParametercalledskipTokenExchangewhich will allow users to retrieve the OAuth authorization_code before it's exchanged for an access_token and id_token.This is necessary for e.g. using this library in an application with a backend server that needs to access a user resource via client_secret (as opposed to the serverless OIDC flow).