# Login Hint is setting password authentication be default

**URL:** <https://community.auth0.com/t/login-hint-is-setting-password-authentication-be-default/111890>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [July 23, 2023, 12:53pm UTC](https://community.auth0.com/t/login-hint-is-setting-password-authentication-be-default/111890 "2023-07-23T12:53:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yarin](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/yarin/32/49188_2.png) [@yarin](https://community.auth0.com/u/yarin)\
**Post date:** [July 23, 2023, 12:53pm UTC](https://community.auth0.com/t/login-hint-is-setting-password-authentication-be-default/111890/1 "2023-07-23T12:53:20Z")

</div>

I am using the new universal login experience.  
The user lands in our page, enters his email and then redirected to auth0 universal login page.  
In between we capture the sign in request, append the organization id to the request to auth0.  
Then the user sees the universal login customised for his organization (tenant).  
In order to save the burden of typing the email twice, I am passing “login\_hint” as mentioned in the docs,  
But when this parameter is used the other auth methods of the organizations (such as Okta) doesnt appear, but only “username password” method.

Why this is behaves like this and is there another way of pre-filling this input without restricting the flow?

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [July 24, 2023, 5:29pm UTC](https://community.auth0.com/t/login-hint-is-setting-password-authentication-be-default/111890/3 "2023-07-24T17:29:00Z")

</div>

Hi @yarin,

Welcome to the Auth0 Community!

> [@yarin](#):
>
> But when this parameter is used the other auth methods of the organizations (such as Okta) doesnt appear, but only “username password” method.

Yes, that is by design. When you pass the `login_hint` parameter in the login request, it will be used to populate the username/email field for the login or signup page. (Reference: [New Universal Login Experience - login\_hint](https://auth0.com/docs/authenticate/login/auth0-universal-login/new-experience#:~:text=You%20can%20specify%20the%20login_hint%20when%20redirecting%20to%20Auth0%2C%20and%20it%20will%20be%20used%20to%20populate%20the%20username/email%20field%20for%20the%20login%20or%20signup%20page.)) By default, it uses the _Username-Password-Authentication_ database connection.

As a workaround, you could pass the `login_hint`, `organization`, and `connection` query parameters in your `/authorize` request. This will allow you to specify the connection that the user will use to log in.

For example:

```auto
https://{yourDomain}/authorize?
    response_type=code&
    client_id={yourClientId}&
    redirect_uri={https://yourApp/callback}&
    scope={scope}&
    audience={apiAudience}&
    state={state}&
    organization={org_id}&
    login_hint={user_email_address}&
    connection={yourConnection}

```

In summary, passing in the `connection` parameter in your login request will let you specify the connection the user will use to authenticate.

Please let me know if you have any questions.

Thanks,  
Rueben

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 7, 2023, 5:29pm UTC](https://community.auth0.com/t/login-hint-is-setting-password-authentication-be-default/111890/4 "2023-08-07T17:29:14Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.