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
Describe the bug
When a user has signed onto the device previously, an attempt to sign in again is presented with a welcome back screen bearing the user's name and a password prompt. However, if the was signed in via an OIDC provider (e.g. Google/Apple), they have no password and this attempt to login will fail with a "No password" error. The form also does not offer them the choice to login with their previous OIDC provider at all.
It seems like this welcome-back behavior needs to be OIDC aware to be effective.
To Reproduce
Steps to reproduce the behavior:
Sign into a client using MAS and an OIDC provider (Google).
Complete login, then logout of the app.
Attempt to login again, you will be presented to return and reauthorize the account with a password.
See error
Expected behavior
I would expect that a returning user would be prompted to use their previous method of 3rd party authorization if they do not have a password.
Smartphone:
Device: iOS
OS: 17.5
Browser: Authenticated Embedded Browser
Version: NA
The text was updated successfully, but these errors were encountered:
Describe the bug
When a user has signed onto the device previously, an attempt to sign in again is presented with a welcome back screen bearing the user's name and a password prompt. However, if the was signed in via an OIDC provider (e.g. Google/Apple), they have no password and this attempt to login will fail with a "No password" error. The form also does not offer them the choice to login with their previous OIDC provider at all.
It seems like this welcome-back behavior needs to be OIDC aware to be effective.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect that a returning user would be prompted to use their previous method of 3rd party authorization if they do not have a password.
Smartphone:
The text was updated successfully, but these errors were encountered: