Changes according to Microsoft OAuth2 v2 changes#10
Open
suhaspan wants to merge 3 commits into
Open
Conversation
…ess token, refresh token, 2.0 me API
Changed URLs to use Microsoft Office v2.0 OAuth with SCOPE to get access token, refresh token, 2.0 me API
Owner
|
Hello @suhaspan. Thanks for contribution. Please can you strip this pull request down to minimal code change related to PR title (Changes according to Microsoft OAuth2 v2 changes )? I don't think changes in license, readme and gemspec are need. I agree on releasing new major version with those endpoint changes. Feel free to ping me if you need any help. |
Author
|
@simi , Removed extra changes. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Changes according to Microsoft OAuth2 v2 changes