Possibility to register wordpress authenticate filter. #236
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.
All Submissions:
Changes proposed in this Pull Request:
This PR is a replacement for #130
Added authenticate_filter to allow login via a default wordpress Login form. The user is not forwarded to Provider Server.
If we are owner of both instances (a WP site and User Provider Server), we can allow the WP instance to know a user credentials - so user can login direct via Login Form.
The 'new' validate($response_token) function is not new. the functions body is moved from authentication_request_callback() and adapted to reuse with new authenticate_filter() function.
Closes # .
How to test the changes in this Pull Request:
Other information:
Changelog entry