Do not send useCookiesForTransactions to authorize request #673
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.
By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description
useCookiesForTransactions was being sent to the /authorize endpoint which seems like not intended.
This appears to be a common thing, because we rely on allowing any additional parameters to be sent to /authorize, as soon as we start adding additional configurations (for client side use only), they end up being sent to the /authorize endpoint anyway.
We talked about this before, but I guess the SDK would benefit from having the configuration options reconsidered and restructured.
References
auth0/auth0-react#170
Checklist
master