Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default behavior traps in verify email loop #217

Closed
schamp opened this issue Jun 21, 2016 · 3 comments
Closed

default behavior traps in verify email loop #217

schamp opened this issue Jun 21, 2016 · 3 comments

Comments

@schamp
Copy link

schamp commented Jun 21, 2016

If SSO is configured and new signups are configured to require a verified email, after signup if I attempt to log into the wordpress with lock, I see the following message:
screen shot 2016-06-21 at 7 04 17 am

However, I am not sure that the 'login' link is correct here -- the user is already logged in to Auth0, but is prevented from continuing to the wordpress site. However, if I select 'login', I am sent back to lock, which notices I am logged in to Auth0, and then sends me back to this screen in a loop.

If a logout link were presented instead of a login link, it would allow the user to log out of Auth0 instead of getting trapped in a loop. There is no other obvious way to log out of the Auth0 I have a patch for this ready to go, but I saw the filter mechanism set up to allow customization of this error message. I could implement it that way, but it seemed to me like a more sensible default might be a better solution. Shall I submit a pull request?

@glena
Copy link
Contributor

glena commented Jun 21, 2016

I will tackle this. The correct behaviour is to redirect to the logout endpoint before showing this message. This needs a couple of redirection, I will take care as soon as I can.

@schamp
Copy link
Author

schamp commented Jun 21, 2016

Excellent, thank you.

@joshcanhelp
Copy link
Contributor

I'm not seeing this issue occurring anymore so I'm going to close it.

@schamp - Very belated reply here but if you're still seeing this issue, ping me here and I'll take another look.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants