Add WordPress.com as an auth provider #130
Merged
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
added 2 commits
July 8, 2020 00:46
13 tasks
pbrisbin
approved these changes
Jul 8, 2020
|
I think so; I tested it and it doesn't look like there's a need parameterize this further (e.g. to allow custom scopes). |
|
Sorry I lost track of this! I'll merge it this week, once I work out the CI issues in |
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.
The immediate purpose of this PR is to aid in testing #128, as the WordPress.com oauth2 implementation requires form parameter style client credentials when fetching the token. That PR has a link to a live test implementation.
Documentation for this integration is at https://developer.wordpress.com/docs/wpcc/