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

Single sign on shows the login username/password fields briefly before automatically signing in #508

Closed
ghills opened this issue Jul 26, 2018 · 2 comments
Milestone

Comments

@ghills
Copy link

ghills commented Jul 26, 2018

Steps:

  • Plugin configured in Wordpress with SSO enabled.
  • Logged into auth0 account from the same tenant (different application) using the hosted login page.
  • Link is clicked that goes to a Wordpress page that requires login and automatically redirects to the login page.

Expected behavior:

  • User is taken to the login page.
  • Lock widget is loaded and has the "spinner" animation.
  • User is authenticated and redirected to the originally requested page (via redirect URL)

Actual behavior:

  • User is taken to the login page.
  • Lock widget is loaded and shows "spinner" briefly.
  • Spinner animation is removed and the username/password fields are displayed in the lock widget.
  • The page continues working and after a few more seconds redirects the user to the originally requested page.

As you can see, while the SSO works there is some confusion as it looks like it is requiring the user to enter credentials before it completes the SSO. This is mostly a cosmetic thing but may confuse users depending on how long it sits on the page with the login fields present.

@joshcanhelp
Copy link
Contributor

@ghills - Thank you for the report here and detailed repro steps. This is on our radar for the next release. That delay is dependent, in part, on your network speed so a slower speed will take longer to make the necessary SSO call. We'll change that to make the Lock init depend on that check.

Thanks again!

@joshcanhelp joshcanhelp added this to the v3-Next milestone Jul 26, 2018
@ghills
Copy link
Author

ghills commented Jul 26, 2018

Great! Thank you for the quick response.

@joshcanhelp joshcanhelp modified the milestone: v3-Next Aug 9, 2018
@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

2 participants