You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you configure a client application to have a database connection with Requires Usernameenabled 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:
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.
The text was updated successfully, but these errors were encountered:
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:[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.The text was updated successfully, but these errors were encountered: