# Self hosted widget does not display password on the same screen as username **URL:** \ **Category:** OAuth/OIDC\ **Created:** [July 19, 2023, 4:21pm UTC](https://devforum.okta.com/t/self-hosted-widget-does-not-display-password-on-the-same-screen-as-username/24863 "2023-07-19T16:21:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![satin](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@satin](https://devforum.okta.com/u/satin)\ **Post date:** [July 19, 2023, 4:21pm UTC](https://devforum.okta.com/t/self-hosted-widget-does-not-display-password-on-the-same-screen-as-username/24863/1 "2023-07-19T16:21:58Z")
I have been following this thread to see if It can fix my issue, but so far I’ve had no luck. > [@Okta widget throws email and password as separate form for login](https://devforum.okta.com/t/okta-widget-throws-email-and-password-as-separate-form-for-login/24534): > > I am using okta sign in widget and for some reasons it asks to verify the email first and then after clicking the CTA it asks to verify the password. What i want to do is the email and password field should be in a single form, the user fills in both username and password and then he clicks on submit button. Attaching a screenshot for a reference. We want to achieve as attached in the below screenshot, how can we achieve this? ![image](https://global.discourse-cdn.com/oktadev/original/2X/7/7ca2627d616e430236f9abd61e3b448dd14d14b8.png) My application setup is: 1. OIDC based SPA 2. A User group that is assigned to this application. 3. Default “Any Two Factors” authentication policy is assigned to the group. 4. Under Authenticators \>\> Enrollment added a custom policy to manage allowed factors. 5. As mentioned in the thread above, I changed the gloabl session policy settings to “A Password”. I am still getting the widget with only username field to start the auth process. Okta details: Version 2023.07.0 E ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [July 19, 2023, 9:36pm UTC](https://devforum.okta.com/t/self-hosted-widget-does-not-display-password-on-the-same-screen-as-username/24863/2 "2023-07-19T21:36:50Z")
Do you have any Routing Rules enabled for your org/app that would route a user to an external IdP based on their username/user attributes? With Routing Rules enabled, Okta first requests the username so it can determine if the user has a password in Okta or not. If they’re Okta users, the password input will be displayed on the next page, while external users will be redirected to their IdP. ---
**Author:** ![satin](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@satin](https://devforum.okta.com/u/satin)\ **Post date:** [July 26, 2023, 6:38pm UTC](https://devforum.okta.com/t/self-hosted-widget-does-not-display-password-on-the-same-screen-as-username/24863/3 "2023-07-26T18:38:34Z")
Hey, I don’t think I have any external IdP enabled. Okta is the source of truth for the user auth. Edit: Moreover, this seems to work if I input any dummy id which is not part of okta users. It will let me enter the incorrect user name, then on the next screen, password as well. But then trying to signin will fail as expected. ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [February 15, 2024, 11:35pm UTC](https://devforum.okta.com/t/self-hosted-widget-does-not-display-password-on-the-same-screen-as-username/24863/4 "2024-02-15T23:35:50Z")