WordPress lost password form redirects

[anilnatha]

Hello again! I found an issue with the WordPress "lost your password" feature when Authorizer is installed and could use your guidance on how I may fix it.

When a user bypasses our default login and visits our WordPress login page by appending the query string external=wordpress, they can then access the "lost your password" feature. After submitting the 'lost your password' form, the user is redirected to a success view on wp-login.php with the query string ?checkemail=confirm&external=cas. Because Authorizer attempted to send them to our default login page which is CAS by setting external=cas, it causes the success page to break:

If I change external=cas to external=wordpress the page renders correctly and this is where the user should have been sent after submitting the form since they had originally bypassed the default login:

Any ideas on how this may be remedied?

BTW, Thanks again for all your support on getting the proxy updates added, it's been working great for us.

[anilnatha]

Forgot to mention on more thing. The 'login page' link on the success view points to https://my.domain.com/wp-login.php when it probably should point to https://my.domain.com/wp-login.php?external=wordpress since the user bypassed the default login.

[pkarjala]

Hi, thanks for this report! This is definitely a workflow issue that should be redirecting to the WordPress login page if you are using external=wordpress to access the base WordPress login page. We'll work on implementing a solution for this!

[pkarjala]

HI @anilnatha Can you please confirm the exact settings that you currently have on the Advanced tab of your Authorizer Settings page? A screenshot would suffice.

Additionally, do you currently have CAS automatic login checked under the External Service tab in Authorizer?

[anilnatha]

Hi @pkarjala

Here is a screenshot of the the advanced settings:

Additionally, do you currently have CAS automatic login checked under the External Service tab in Authorizer?

Yes, it is enabled.

[pkarjala]

Hi @anilnatha I've just pushed up a code fix to address this issue. The fix will be included in the next Authorizer release.
Thank you again for the report!

[figureone]

Version 3.4.2 has been released with this fix. Thanks!

[anilnatha]

Thank you for addressing the issue @pkarjala and @figureone! I'll update our instance and report back if I encounter any issues.