Not that strange. Different users may belong to different groups which may have different authentication backends. The associated authentication method is brought up once a username has been provided.
I don’t like it when I need to sign in twice for single sign-on. The email/username then tells the system if they need to be directed to another sign in page. Like Google or Microsoft. This then allows you access without having to give them your password.
This reminds me of another annoying one, often related to these routing pages.
I type in my email, then it routes to “create an account”. Or WORSE it mimmicks the thing the OP is complaining aboit and says it sent me a verification email, then prompts me to make an account.
Like fucker, I have a dozen+ email addresses, if my email isn’t an account, just tell me so I can try a different one.
Not that strange. Different users may belong to different groups which may have different authentication backends. The associated authentication method is brought up once a username has been provided.
if your choice of api route directly affects your auth flow something is very wrong.
I don’t like it when I need to sign in twice for single sign-on. The email/username then tells the system if they need to be directed to another sign in page. Like Google or Microsoft. This then allows you access without having to give them your password.
You can do that as part of an OAuth workflow. You don’t need to have them on separate pages for that to happen.
Yes, but, it also lets them slurp up email addresses. Routing users is legit tho.
This reminds me of another annoying one, often related to these routing pages.
I type in my email, then it routes to “create an account”. Or WORSE it mimmicks the thing the OP is complaining aboit and says it sent me a verification email, then prompts me to make an account.
Like fucker, I have a dozen+ email addresses, if my email isn’t an account, just tell me so I can try a different one.