Do Not Merge: v5.0.3 + fixed validation ordering #2
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
* Attempt at fixing information disclosure vulnerability. * Add `#as_json` method and attrs serialization restriction for Application model * [ci skip] Add documentation for serialization Co-authored-by: Nikita Bulai <[email protected]>
- Calling public method redirectable should do the right thing regardless of validation state Signed-off-by: Kevin Lai <[email protected]> Co-authored-by: Kevin Lai <[email protected]>
shirish-pampoorickal
changed the title
shirish-pampoorickal
changed the title
urnf
reviewed
Nov 11, 2021
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.
NOTE: This PR starts from Doorkeeper 5.0.3 as a base. This is intended to serve as a temporary source for our gem in the interim while we upgrade to Ruby 2.4+. This branch is pointed to from our gemfile, do not merge this PR!
Summary
We are fixing
redirectable?returning the wrong result as a consequence of a different error name type. This should function correctly independently of the error name type.In base Doorkeeper, there is a PR and commit that the maintainer is looking to push into the latest 5.2 that fixes the issue in one way doorkeeper-gem@444fdbe where their intent is that validations (and the error response generated) need to happen in a very specific order and would avoid running into this issue.