Add filter for rest_api_can_edit_user_and_update_two_factor_options #689
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.
What?
Introduce a new filter hook in the
Two_Factor_Core::rest_api_can_edit_user_and_update_two_factor_options
method.Why?
To allow developers to programmatically control whether REST API endpoints related to Two-Factor authentication can edit a specific user’s settings.
How?
Added a new filter,
two_factor_rest_api_can_edit_user
, which allows overriding the default behavior by modifying the return value of therest_api_can_edit_user_and_update_two_factor_options
method.Testing Instructions
The following snippet disables Two-Factor-related REST API endpoints (
rest_setup_totp
,rest_delete_totp
, andrest_generate_codes
) for a specific user (user ID 123):Testing Instructions
Changelog Entry
Added - New
two_factor_rest_api_can_edit_user
filter to control edit permissions via the REST API for specific users