`onLogin()` silently discards Auth0 error responses
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- authentication
Research direction
Start at the onLogin() callback around lines 545–548, where the error path redirects to /, and compare it with v4’s WP_Auth0_LoginManager::die_on_login() behavior. Reproduce the callback using the provided error parameters and verify that a failed login shows an error indication instead of silently redirecting to /.
Written by the indexing model from the issue text.
Description
Checklist
- I have looked into the Readme and the documentation, and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Description
When Auth0 returns an error/error_description on the login callback (expired password, breached-password block, blocked account, etc.), onLogin() redirects to / and exits with no message shown. v4's equivalent (WP_Auth0_LoginManager::die_on_login()) displayed "There was a problem with your log in: {description} [error code: {code}]".
Expected: some indication is shown to the user that login failed and why.
Reproduction
- Trigger any Auth0-side login error (e.g. visit
wp-login.php?error=access_denied&error_description=test&state=<valid-state>, or trigger a real rejection like a blocked/breached-password account). - Observe the browser is redirected to
/with no error message, indistinguishable from a no-op.
Additional context
// line ~545-548
if (null !== $error) {
wp_redirect('/');
exit;
}
wp-auth0 version
5.6.1
WordPress version
7.1
PHP version
8.4
- Dominant language
- PHP
- Stars
- 182
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/wordpress
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
Scope: Documentation
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Roadmap: Backlog
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ProfessionalWiki/NeoWiki#1525 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
OpenConext/OpenConext-engineblock#2122 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·