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

Issue with HRD on Sign Up if database connection has requires username enabled #1301

Closed
jmangelo opened this issue Mar 21, 2018 · 2 comments
Closed

Comments

@jmangelo
Copy link

Originally reported at: https://community.auth0.com/t/auth-bug-saml-required-username-database-connections/10257


If you configure a client application to have a database connection with Requires Username enabled and a SAML enterprise connection with an associated email domain of contoso.com then if you perform the following steps in Lock 11.4.0:

  1. Show Lock.
  2. Select the Sign Up section.
  3. Input an email like [email protected] in the email field.

then Lock should detect that the email is associated with an enterprise connection and display the SSO enabled option. However, Lock won't show SSO enabled even though the email domain matches an enterprise connection.

As additional information, if you then enter [email protected] also as the username value Lock does show the SSO enabled option so it seems that when requires username option is available Lock gets the username instead of the email for the purposes of checking for SSO against enabled enterprise connections, however, it should always pick from the email field as HRD is based on email addresses.

@matthieualouis
Copy link

Hi Auth0 team, do you have any timeline for a fix to this bug?

It's going to be blocking us from using the Auth0 Lock widget pretty soon.

@luisrudge
Copy link
Contributor

fixed in #1278

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants