[Feat]: Different login flow when Email authentication disabled
Is it possible to change the login flow when Email authentication is disabled?
Rather than /org/12345678912345678912343/auth/login taking the user to this screen:
It goes directly to the next screen:
Agreed, we don't need do duplicate the email as it can be pulled from Oauth; However, it only makes sense when we're in Enterprise mode (single workspace) or when there is only one workspace in SAAS mode.
In case there are different workspaces, it makes sense to first ask user for email - because Oauth providers are defined per workspace, so first we need to know username and display their workspace to select (that's what happens now)
Ah, OK. I was thinking that it would only apply when the workspace is specified in the login URL.
When an unauthorised user attempts to access my app, they are redirected to /org/12345678912345678912343/auth/login
I'm experiencing the same issue. When email authentication is disabled and OAuth is enabled, the login flow still prompts users to enter their email before redirecting to the OAuth verification page. The expected behavior is that the email input screen should not be displayed when email authentication is disabled and OAuth is the only enabled login method.
This behavior creates unnecessary friction in the login process. It would be great if the system could directly redirect users to the OAuth verification page without requiring an email input step in this scenario.
The Login flow has now been updated. If Email Authentication is disabled, then Email field is not shown and Users are directly redirected to OAuth screen ( if configured ).
@biankasyo , @meretrout , @martkaczmarek , kindly let us know your feedback and feel free to open this ticket if you guys face any issue.