Closed zachsa closed 3 years ago
It was a design choice to keep the password and Google login flows separate - otherwise things get complicated and not-so-obvious - e.g. allow the password field to be optional and detect a gmail address and trigger the Google flow from the login button... It doesn't make sense to capture the user's Google password, we can't forward that to Google and it would break the OAuth2 security model anyway.
If a @saeon.ac.za account was created using password signup first, then the user can log in via either method - maybe a little inconsistent but it doesn't cause any problems. However if the account was first created via Google, then it has no password.
So there are two options here:
Either or both sound good to me!
Hi Mark,
Amelia has previously logged into the Identity Server using the 'SAEON Staff' button. This morning she was trying to login via username/password with the same email and couldn't login.
Steps:
Any ideas how to make this more pleasant for users?