This repository was archived by the owner on Sep 1, 2025. It is now read-only.
Fix oauth new behavior after upgrading to v2#25
Merged
Conversation
gitviola
approved these changes
Dec 4, 2019
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After including latest changes in a new monocle branch some e2e tests were broken when accessing stuart-api. Part of those changes were upgrading oauth version from 0.9 to 2.0. When reading the changelog we realized "application/json" serializing wasn't the default anymore so after the upgrade the token was being stored as the full json string.
With this change we explicitly set "application/json" as the content type and Jason as the serializer.
Edit: https://github.com/scrogson/oauth2/blob/master/CHANGELOG.md#v100-2019-03-13