Allow whitelisting API endpoints to skip DT auth requirement #2110
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
|
Looks good. Lets move this to the security tab instead of the general one. |
|
That makes sense. It's moved now. @corsacca |
|
Thanks @cairocoder01! |
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.
Certain third party plugins add API endpoints that needs to not have authentication on them that DT enforces by default. There is currently a filter that can whitelist endpoints via plugin, but this adds a simple way in core to add endpoints that should be allowed to pass through.
For reference, my use case is the Wordfence plugin that has a central dashboard that hits an API endpoint for remote management and configuration.