refactor(login): validate same origin for redirect target url after login #181
Conversation
This file contains 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
emmenko
added
🙏 Status: Dev Review
tdeekens
approved these changes
Dec 5, 2018
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.
To prevent possible unwanted redirects to 3rd party "malicious" websites after the user logs in, we should check that the
redirectToquery parameter matches the currentOrigin.So if you're in
https://mc.commercetools.com/login, theredirectTois valid if it contains the same originhttps://mc.commercetools.com(e.g.https://mc.commercetools.com/my-project/orders).To make the validation possible, the
redirectTonow contains theorigin, where previously it only contained the uri path.