WordPress Plugin for Auth0 Authentication
🚀 Getting Started - 💻 SDK Usage - 📆 Support Policy - 💬 Feedback
- PHP 8.0+
- Most recent version of WordPress
- Database credentials with table creation permissions
Please review our support policy on specific PHP and WordPress versions and when they may exit support in the future.
The plugin supports installation through Composer, and is WPackagist compatible. This approach is preferred when using Bedrock or WordPress Core, but will work with virtually any WordPress installation.
When using Composer-based WordPress configurations like Bedrock, you'll usually run this command from the root WordPress installation directory. Still, it's advisable to check the documentation the project's maintainers provided for the best guidance. This command can be run from the wp-content/plugins sub-directory for standard WordPress installations.
composer require symfony/http-client nyholm/psr7 auth0/wordpress:^5.0
Note on Composer Dependencies
When installed with Composer, the plugin depends on the presence of PSR-18 and PSR-17 library implementations. The require command above includes two such libraries (symfony/http-client and nyholm/psr7) that satisfy these requirements, but you can use any other compatible libraries that you prefer. Visit Packagist for a list of PSR-18 and PSR-17 providers.
If you are using Bedrock or another Composer-based configuration, you can try installing auth0/wordpress without any other dependencies, as the implementations may be satisfied by other already installed packages.
Note PHP Standards Recommendations (PSRs) are standards for PHP libraries and applications that enable greater interoperability and choice. You can learn more about them and the PHP-FIG organization that maintains them here.
After installation, you must activate the plugin within your WordPress site:
- Open your WordPress Dashboard.
- Select 'Plugins' from the sidebar, and then 'Installed Plugins.'
- Choose 'Activate' underneath the plugin's name.
- Sign into Auth0. If you don't have an account, it's free to create one.
- Open 'Applications' from your Auth0 Dashboard, and select 'Create Application.'
- Choose 'Regular Web Application' and then 'Create.'
- From the newly created application's page, select the Settings tab.
Please prepare the following information:
- Note the Domain, Client ID, and Client Secret, available from the newly created Application's Settings page. You will need these to configure the plugin in the next step.
- From your WordPress Dashboard's General Settings page, note your WordPress Address and Site Address URLs. We recommend you read our guidance on common WordPress URL issues.
Continue configuring your Auth0 application from its Settings page:
- Allowed Callback URLs should include the URL to your WordPress site's
wp-login.php.- In most (but not all) cases, this will be your WordPress Address with
/wp-login.phpappended. - Please ensure your site is configured never to cache this URL, or you may see an "invalid state" error during login.
- In most (but not all) cases, this will be your WordPress Address with
- Allowed Web Origins should include both your WordPress Address and Site Address URLs.
- Allowed Logout URLs should consist of your WordPress Address.
Common WordPress URL Issues
- These must be the URLs your visitors will use to access your WordPress site. If you are using a reverse proxy, you may need to manually configure your WordPress Address and Site Address URLs to match the URL you use to access your site.
- Make sure these URLs match your site's configured protocol. When using a reverse proxy, you may need to update these to reflect serving over SSL/HTTPS.
Troubleshooting
If you're encountering issues, start by checking that your Auth0 Application is setup like so:
- Application Type must be set to Regular Web Application.
- Token Endpoint Authentication Method must be set to Post.
- Allowed Origins (CORS) should be blank.
Scroll down and expand the "Advanced Settings" panel, then:
- Under OAuth:
- Ensure that JsonWebToken Signature Algorithm is set to RS256.
- Check that OIDC Conformant is enabled.
- Under Grant Types:
- Ensure that Implicit, Authorization Code, and Client Credentials are enabled.
- You may also want to enable Refresh Token.
Upon activating the Auth0 plugin, you will find a new "Auth0" section in the sidebar of your WordPress Dashboard. This section enables you to configure the plugin in a variety of ways.
For the plugin to operate, at a minimum, you will need to configure the Domain, Client ID, and Client Secret fields. These are available from the Auth0 Application you created in the previous step. Once configured, select the "Enable Authentication" option to have the plugin begin handling authentication for you.
We recommend testing on a staging/development site using a separate Auth0 Application before putting the plugin live on your production site.
The plugin uses dedicated database tables to guarantee high performance. When the plugin is activated, it will use the database credentials you have configured for WordPress to create these tables.
Please ensure your configured credentials have appropriate privileges to create new tables.
The plugin uses WordPress' background task manager to perform important periodic tasks. Proper synchronization between WordPress and Auth0 relies on this.
By default, WordPress' task manager runs on every page load, which is inadvisable for production sites. For best performance and reliability, please ensure you have configured WordPress to use a cron job to run these tasks periodically instead.
The plugin is built on top of Auth0-PHP v8 — Auth0's full-featured PHP SDK for Authentication and Management APIs.
For custom WordPress development, please do not extend the plugin's classes themselves, as this is not supported. Nearly all of the plugin's APIs are considered internal and will change over time, most likely breaking any custom extension built upon them.
Instead, please take advantage of the full PHP SDK that the plugin is built upon. You can use the plugin's getSdk() method to retrieve a configured instance of the SDK, ready for use. This method can be called from the plugin's global wpAuth0() helper, which returns the WordPress plugin itself.
<?php
$plugin = wpAuth0(); // Returns an instanceof Auth0\WordPress\Plugin
$sdk = wpAuth0()->getSdk(); // Returns an instanceof Auth0\SDK\Auth0Please direct questions about developing with the Auth0-PHP SDK to the Auth0 Community, and issues or feature requests to it's respective repository. Documentations and examples on working with the Auth0-PHP SDKs are also available from it's repository.
- Our PHP version support window mirrors the PHP release support schedule. Our support for PHP versions ends when they stop receiving security fixes.
- As Automattic's stated policy is "security patches are backported when possible, but this is not guaranteed," we only support the latest release marked as "actively supported" by Automattic.
| Plugin Version | WordPress Version | PHP Version | Support Ends |
|---|---|---|---|
| 5 | 6 | 8.2 | Dec 2025 |
| 8.1 | Nov 2024 | ||
| 8.0 | Nov 2023 | ||
| 4 | 6.0, 6.1 | 8.0 | Jun 2023 |
| 5 | 7.4, 8.0 | Jun 2023 |
Composer and WordPress do not offer upgrades to incompatible versions. Therefore, we regularly deprecate support within the plugin for PHP or WordPress versions that have reached end-of-life. These deprecations are not considered breaking changes and will not result in a major version bump.
Sites running unsupported versions of PHP or WordPress will continue to function but will not receive updates until their environment is upgraded. For your security, please ensure your PHP runtime and WordPress remain up to date.
We appreciate feedback and contribution to this repo! Before you get started, please see the following:
To provide feedback or report a bug, please raise an issue on our issue tracker.
Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
Auth0 is an easy-to-implement, adaptable authentication and authorization platform.
To learn more checkout Why Auth0?
This project is licensed under the MIT license. See the LICENSE file for more info.