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

bug: login with loginHint does not skip the username input #6759

Open
1 of 4 tasks
ImSingee opened this issue Nov 3, 2024 · 2 comments
Open
1 of 4 tasks

bug: login with loginHint does not skip the username input #6759

ImSingee opened this issue Nov 3, 2024 · 2 comments
Labels
feature-request Something cool or not cool

Comments

@ImSingee
Copy link
Contributor

ImSingee commented Nov 3, 2024

Describe the bug

If invoked with a loginHint, the username/email filled in correctly, but user still have to click "Sign in" again in the logto page.

For example, on the login page, the user has already input the email:

image

Call logto signIn method with a loginHint, then the user will be redirected to the following page:

image

The user has to click the Sign in again, this is a terrible UX.

Expected behavior

Show the page as if user clicks the Sign in in logto.

For example, directly navigate the user to the following page:

image

How to reproduce?

logtoClient..signIn({
      redirectUri: `${location.protocol}//${location.host}/login/callback`,
      firstScreen: "sign_in",
      loginHint: '[email protected]`,
    });

Context

  • Logto Cloud
  • Self-hosted, Logto version =
    • Container (Docker image)
    • Raw Node.js

BTW, I also try the identifier:sign_in, but it doesn't work either.

@ImSingee ImSingee added the bug Something isn't working label Nov 3, 2024
@darcyYe
Copy link
Contributor

darcyYe commented Nov 12, 2024

Thank you for your suggestion. In fact, this isn't a bug, but more like a feature request.
It could be considered to support: automatically moving to the next step once the form is filled out. However, the reality is that it's hard to determine if the user still wants to modify the entered values after filling out the form, so it's more reasonable to let the user choose to proceed to the next step themselves.

@darcyYe darcyYe added feature-request Something cool or not cool and removed bug Something isn't working labels Nov 12, 2024
@darcyYe
Copy link
Contributor

darcyYe commented Nov 12, 2024

Would you like to convert this issue to be a feature request and describe your needs? The team will review GitHub issues every week and have internal discussion to determine whether we should support those feature requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Something cool or not cool
Development

No branches or pull requests

2 participants