You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -681,7 +681,7 @@ add_filter(
681
681
## Credits
682
682
683
683
-[PHP-JWT from firebase](https://github.com/firebase/php-jwt)
684
-
-[JWT Authentication for WP REST API](https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/)
684
+
-[JWT Authentication for WP REST API](https://wordpress.org/plugins/jwt-authentication-for-wp-rest-api/). My _JWT-Auth_ plugin was a "copy-then-modify" of _JWT Authentication for WP REST API_ plugin.
685
685
-[Devices utility by pesseba](https://github.com/pesseba)
@@ -707,6 +707,13 @@ You can help this plugin stay alive and maintained by giving **5 Stars** Rating/
707
707
3. Other error responses
708
708
709
709
== Changelog ==
710
+
= 2.0.0 =
711
+
- Breaking change: rename `jwt_auth_valid_token_extra` filter to `jwt_auth_extra_token_check`. Please check if you use this filter.
712
+
- Breaking bugfix: the actual http statusCode didn't follow the response statusCode. Now the actual http statusCode follows the response statusCode.
713
+
- New feature: connected device. Thanks @pesseba.
714
+
- Might be a breaking change: Add WordPress & WC default endpoints to `jwt_auth_default_whitelist` to prevent error when visiting WordPress admin area.
715
+
- Documentation: prevent misleading example by updating the `jwt_auth_whitelist` usage.
716
+
710
717
= 1.4.2 =
711
718
- Bugfix: add `permission_callback` argument since it's required in WP 5.5
0 commit comments