Skip to content

Commit

Permalink
Update release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
joshcanhelp committed Apr 18, 2019
1 parent 65d048c commit 9122dfd
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
- The default Lock version has been updated from 11.5 to 11.15. If you have never changed the Lock URL, this update will be automatic for this and future releases. If you have updated the Lock URL in the past, your custom URL has been retained. We recommend using the latest tested version of Lock, which can be done by turning the "Use Custom Lock JS URL" option off on the **Advanced** tab of the plugin settings. Please see the [Lock changelog](https://github.com/auth0/lock/blob/master/CHANGELOG.md) (v11.6.0 to v11.15.0) for information on changes to the embedded login form.
- Core WordPress login form display handling has been changed to improve security and maintainability. Please review the "Original Login Form on wp-login.php" option on the **Basic** tab of the plugin settings to make sure this is set properly for your site.
- Site administrators can now rotate the migration token in the **Advanced** tab of the plugin settings. This change will occur right after confirmation and must be updated in the database Connection immediately. Please see our [documentation page on User Migration](https://auth0.com/docs/cms/wordpress/user-migration) for more information about configuring and troubleshooting this feature.
- The "API Token" field in the **Basic** tab of the plugin settings has been removed. All Management API functionality now uses a Client Credentials grant, which is set up automatically when you run the Setup Wizard. The only scopes required for the plugin are now `read:users` and `update:users`. Configuration steps for this can be found [here](https://auth0.com/docs/cms/wordpress/configuration#authorize-the-application-for-the-management-api) but if your site is already working as expected currently then no action is required for this update.
- The "API Token" field in the **Basic** tab of the plugin settings has been removed. All Management API functionality now uses a Client Credentials grant, which is set up automatically when you run the Setup Wizard. The only scopes required for the plugin are now `read:users` and `update:users`. Configuration steps for this can be found [here](https://auth0.com/docs/cms/wordpress/configuration#authorize-the-application-for-the-management-api) but if your site is already working as expected currently then no action is required for this update to function but any additional scopes for your WordPress application should be removed from the Management API at some point.
- The "Password Policy" setting on the **Features** tab has been removed. This setting must be managed in the settings for the [database Connection](https://manage.auth0.com/#/connections/database) being used going forward. No changes were made to the connection, just the ability to manage it in WordPress.
- The "Multifactor Authentication (MFA)" switch on the **Features** tab has been removed. This setting must be managed in the [Auth0 dashboard](https://manage.auth0.com/#/mfa) going forward. No changes were made to how this works, just the ability to manage it in WordPress.
- The "FullContact," "Store Geolocation", and "Store Zipcode Income" settings on the **Features** tab have been removed. These settings must be managed in [Rules](https://manage.auth0.com/#/rules) going forward. No changes were made to how these features work, just the ability to manage them in WordPress.
Expand All @@ -22,6 +22,7 @@

**Notes for developers**

- A `wp_auth0_get_option()` function has been added to get an option value. Please use this going forward instead of `WP_Auth0_Options::Instance()->get()`.
- As mentioned above, a Management API token can no longer be provided manually (except in the Setup Wizard). The token is now obtained automatically using a Client Credentials grant and stored in a transient along with the allowed scopes. You can get the existing token with `WP_Auth0_Api_Client_Credentials::get_stored_token()` and check for necessary scopes with `WP_Auth0_Api_Client_Credentials::check_stored_scope()`. If you need to get a new token, use `\WP_Auth0_Api_Client_Credentials::call()`.
- If you are using any of the `WP_Auth_*` classes in a custom plugin or theme, please note that there have been many deprecations in the last several releases. All deprecated classes, methods, and functions will be removed in the next major release so please review your custom code and make the appropriate changes.
- The `auth0_sso_auth0js_url` filter has been added that lets you override the default CDN URL for Auth0.js when doing an SSO check on the `wp-login.php` page.
Expand Down

0 comments on commit 9122dfd

Please sign in to comment.