Skip to content

Releases: auth0/wordpress

5.3.0

15 May 20:57
9b0cb9b
Compare
Choose a tag to compare

Fixed

4.6.2

12 Jul 16:49
Compare
Choose a tag to compare

Full Changelog

Fixed

  • Resolved an issue with corrupted JSON payloads.

4.6.1

09 Jul 00:56
Compare
Choose a tag to compare

Changed

  • Tested against WordPress 6.5.5 w/ PHP 8.3.
  • Improved translated string handling.

Fixed

  • Resolved issue with ?wle parameter handling.

5.2.1

04 Jun 03:26
cf53efe
Compare
Choose a tag to compare

Fixed

  • Resolves an issue in which the fallback URI secret isn't shown. #903 (HPiirainen)
  • Resolves a compatibility issue with changes in WordPress 6.5 causing invalidated sessions. (evansims)

4.6.0

11 Jan 21:15
257c59d
Compare
Choose a tag to compare

Full Changelog

Added

Changed


You can verify the signature of a downloaded release archive using OpenSSL. Download the public signing key from the GitHub repository and save it to the same directory as the .ZIP and .SIGN files provided with this release, then run the following:

openssl dgst -verify public-signing-key.pub -keyform PEM -sha256 -signature Auth0_WordPress_Plugin_4.6.0.zip.sign -binary Auth0_WordPress_Plugin_4.6.0.zip

5.2.0

12 Dec 19:16
0d5aef8
Compare
Choose a tag to compare

Added

  • feat(SDK-4734): Implement support for Back-Channel Logout #882 (evansims) ¹

Changed

  • Bumped auth0-php dependency version range to ^8.10.
  • Raised the minimum supported PHP version to 8.1.
  • Confirmed support for WordPress 6.4. Updated metadata to reflect support.

Note

¹ To use this feature, an Auth0 tenant must have support for it enabled.

5.1.0

24 Jul 08:05
Compare
Choose a tag to compare

Added

  • Organization Name support was added for Authentication API and token handling ¹

Updated

  • Bumped tested WordPress version to 6.3.0.
  • Bumped auth0-php dependency version range to ^8.7.
  • Updated telemetry to indicate wordpress package (previously wp-auth0.)

Note
¹ To use this feature, an Auth0 tenant must have support for it enabled. This feature is not yet available to all tenants.

4.5.0

30 Jan 05:38
56a0ceb
Compare
Choose a tag to compare

Full Changelog

Added

Fixed

  • auth0_update_meta filter not passing $value #847 (QWp6t)
  • wpa0_should_create_user filter not registering with correct parameter count #843 (alyxb)

You can verify the signature of a downloaded release archive using OpenSSL. Download the public signing key from the GitHub repository and save it to the same directory as the .ZIP and .SIGN files provided with this release, then run the following:

openssl dgst -verify public-signing-key.pub -keyform PEM -sha256 -signature Auth0_WordPress_Plugin_4.5.0.zip.sign -binary Auth0_WordPress_Plugin_4.5.0.zip

5.0.1

13 Dec 00:01
Compare
Choose a tag to compare

Full Changelog

Fixed

  • Resolves an issue which sometimes prevented the plugin from being activated on WordPress 6

5.0.0

28 Oct 21:12
5bb7dec
Compare
Choose a tag to compare

Full Changelog

Introducing V5 of WP-Auth0 ("Login by Auth0"), a major redesign and upgrade to our WordPress integration plugin. V5 includes many new features and changes:

  • WordPress 6 and PHP 8 support
  • Integration with the Auth0-PHP SDK, and access to its entire API (including Management API calls)
  • High performance background sync using WordPress' Cron feature
  • "Flexible identifier" support, allowing users to sign in using multiple connection types without requiring extra configuration
  • Expanded control over how sign ins without matching existing WordPress accounts are handled
  • Enhanced session pairing between WordPress and Auth0, including session invalidation, access token refresh, and more.

V5 represents a major step forward for our WordPress plugin, and we're excited to see what you build with it!

It's important to note, if you wrote custom theme code or plugins for your WordPress site that targeted previous versions of the plugin, you may need to adjust those themes or plugins to adapt to the new version. We will be rolling this release out to the WordPress plugin store in the near future. Meanwhile, you can manually install the package using Composer using the instructions in the README.