Skip to content

Releases: auth0/wordpress

5.0.0-BETA0

03 Oct 06:22
e84833e
Compare
Choose a tag to compare
5.0.0-BETA0 Pre-release
Pre-release

⚠️ Version 5.0 of our plugin is now available in Beta. This release adds a significant number of features. We do not recommend using this release in a production environment yet. There are breaking changes and some functionality remaining to be implemented. In particular, the migration process needs further development and testing. As we move toward General Availability, please be aware that further beta releases may contain additional breaking changes.

A new Beta Channel version of the plugin will be available from the WordPress plugin marketplace soon, which will enable you to opt into receiving updates to new development releases as they happen.

New Features

  • PHP 8.0 Support — The plugin has been redesigned to use PHP 8.0+ language features.
  • Flexible Connection Matching — This allows users to sign in using multiple connections to the same account. For example, with this you can now sign in using your standard email-password, or social connections you've enabled. Any connection works so long as the authenticating account shares the same (verified) email address.
  • Absentee Account Handling — You can now choose different behaviors for handling when a user signs in successfully, but an account doesn't exist matching the email. Although Auth0 Database Connections have always handled this well on the API side with the 'Disable Sign Ups' toggle, social connections are trickier in cases where that option doesn't exist. You can now choose to deny those types of authentication requests, or dynamically create new accounts for those users.
  • WP-Cron support — The plugin now leverages the WP background task scheduler to improve performance. Because real time Management API calls can sometimes fail (rate limits, network congestion on ones hosting provider, etc.) we can now batch changes for WP customers with high traffic sites to more efficiently bring their CMS and Auth0 databases in sync.
  • Session Pairing — WordPress sessions are not completely managed by the plugin, ensuring scenarios like token expiration and refresh tokens are honored and properly acted upon.
  • PSR-18, PSR-17 and PSR-7 Support — All networking functions of the plugin have been rewritten to use the PHP-FIG standards for HTTP messaging. This also removes the library's dependency on Guzzle.
  • WP_Object_Cache support — Caching now uses the native WP_Object_Cache API, for enhanced storage options through third party plugins. In particular, this is now used for JWKS caching, enabling improved performance.

Breaking Changes

  • PHP 8.0.0 is now the minimum supported version.
  • Embedded login support has been deprecated, and Universal Login is now required.
  • All auth0_ and a0_ prefixed functions have migrated into classes beneath the Auth0\WordPress namespace.
  • All previous JWT processing using third-party libraries has been removed. This is now handled by Auth0's PHP SDK.
  • Auth0\WordPress\Plugin handles the underlying Auth0-PHP SDK initialization and configuration.
  • Auth0\WordPress\Actions\Authentication now handles all authentication functions, and acts as the core for the various WordPress hooks used throughout the system.
  • Auth0\WordPress\Actions\Configuration now handles all Admin UI rendering functions. A new configuration database storage format has been established which will supersede the previous V4 method.
  • Auth0\WordPress\Actions\Sync manages the new WP-Cron scheduled task functions.
  • Sessions have been reworked to support the new Auth0 PHP SDK 8.0+ format.

Additional new features and changes may be added before this new version is released as stable.

4.4.0

15 Oct 12:54
79eccf6
Compare
Choose a tag to compare

Full Changelog

Added

  • Enable passing extra custom parameters to the New Universal Login #834 (evansims)
  • Update tests to use PHPUnit 7 and Docker #835 (evansims)

Fixed

  • Skip email sync with Auth0 when we know the update is coming from Auth0 #831 (drobin03)

4.3.1

15 Sep 00:20
5e364d6
Compare
Choose a tag to compare

Full Changelog

Fixed

  • Update client configuration url for embedded logins #832 (evansims)

4.3.0

26 Mar 12:51
7504cc0
Compare
Choose a tag to compare

Full Changelog

Added

4.2.0

11 Feb 20:57
b4a309e
Compare
Choose a tag to compare

Full Changelog

Added

Changed

Fixed

4.1.1

23 Oct 18:28
Compare
Choose a tag to compare

Full Changelog

Fixed

4.1.0

22 May 21:50
Compare
Choose a tag to compare

Full Changelog

Closed issues

  • With a custom domain, JWKs aren't being fetched from the correct domain #790

Changed

Fixed

4.0.0

31 Mar 17:24
Compare
Choose a tag to compare

Full Changelog

This is a major release with breaking changes!

In addition to the minimum PHP version being updated from 5.3 to 7.0, there are many breaking removals and changes that are covered in the migration guide included in this release.

Closed issues

  • pt-BR language is not being installed #760
  • Authorization Extension, groups, roles not showing up #701
  • Using the auth0 word in the URL path triggers an authorization code exchange #351

Added

  • PHPCS security scan, sanitization and escaping improvements, and removed custom admin styling (see commits for details)
  • Add settings validation to import #777 (joshcanhelp)
  • Add ability to break cache if RS256 ID token kid is not found #770 (joshcanhelp)
  • Remove error_log calls and add auth0_insert_error action #763 (joshcanhelp)
  • Get new access token via refresh token API #730 (albeja)
  • feature/Adding Brazilian Portuguese translations #729 (niugait)
  • Add wpa0_user_data filter before creating WP_User #717 (horike37)
  • Add check for GET and POST globals for state validation #707 (joshcanhelp)

Changed

Removed

Fixed

3.11.3

30 Jan 19:22
Compare
Choose a tag to compare

Full Changelog

Security

  • Fix potential XSS on wp-login.php override page #768 (kinabalu)

3.11.2

17 Jan 22:15
Compare
Choose a tag to compare

Full Changelog

Important note for sites using the Implicit Login Flow setting: The upcoming changes to SameSite handling in multiple browsers will require sites using the Implicit Login Flow setting to also be served on a secure channel (callback URL using "https"). This setting will be removed in the upcoming major version but is patched for sites that need time to migrate.