Username/password inputs showing for universal login despite being disabled for application

Our application only has social logins enabled (username-password db connection is disabled) but the universal login page is still showing the email/password text inputs. For what it’s worth, when we switch to the “classic” login page the inputs are missing, but the “universal” login page still includes them.

Hi @cooper.astle

Welcome to the Auth0 Community!

By disabling the database connection from the application, that should not longer show the email and password options. I have double checked on my tenant and this is what I see:

You might have a different Database connection enabled.

If you have any other questions, feel free to leave a reply!

Kind Regards,
Nik

Hey @nik.baleca, thanks for the reply. We don’t have a db connection enabled in the “Applications” tab for our specific app, but we do have the “default directory” set as “Username-Password-Authentication” It appears removing this hides it from the login page.
Is it intentional that this behavior is different between the classic vs universal login experience?

Hi again!

As mentioned by our documentation:

  • Default Directory: Name of the default connection to be used for both the Resource Owner Password Flow and Universal Login Experience. Its value should be the exact name of an existing connection for one of the following strategies: auth0-adldap, ad, auth0, email, sms, waad, or adfs.

This settings is intended to be used for the Universal Login or if the resource owner password flow is configured. The discrepancy between Classing and Universal login is to be expected in this scenario.

Hope that helps!

Kind Regards,
Nik

1 Like

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