Fixed automatic setup process for public sites #370
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
…tings field that defaults to system Management API audience if blank; updating docs links; adding client update procedure from DB v15 to DB v16; adding new scopes to consent process to create client grant
joshcanhelp
force-pushed
the
fixed-auto-setup-process
branch
from
5ee767f to
79a9442
Compare
cocojoe
changed the title
cocojoe
approved these changes
Jan 24, 2018
Merged
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
Main goal here is moving from storing the API audience from the API token to creating a settings field to hold one with the system Management API audience (most likely to be used in the vast majority of installs) as a default.
Also:
WP_Auth0_Api_Client::get_client_token()do use recommended Content-Type headersite_url()update