-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify recognised email and a login confirmation screen #86
Comments
xtuc
added a commit
to xtuc/wildebeest
that referenced
this issue
Jan 30, 2023
xtuc
added a commit
to xtuc/wildebeest
that referenced
this issue
Jan 30, 2023
xtuc
added a commit
that referenced
this issue
Jan 30, 2023
xtuc
added a commit
that referenced
this issue
Jan 30, 2023
dario-piotrowicz
pushed a commit
that referenced
this issue
Jan 30, 2023
takesato
pushed a commit
to takesato/wildebeest
that referenced
this issue
Aug 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is common after a client requests authorization, before the authorization completes, the instance has a screen showing that a client is requesting certain oauth permissions of an account, and the user needs to manually confirm the authorization.
Current behaviour
The entire authorization flow completes by itself.
Expected behaviour
![image](https://user-images.githubusercontent.com/292204/212037310-65416a8f-4c72-478d-8c99-b9174379a99f.png)
An example of such screen from Mastodon. Besides asking the user to confirm permissions, one can also choose to logout of current account and login to another one if needed, which currently is not possible. Also in case several emails/accounts are added into Zero Trust, it is unclear under which account is currently logged into. For this, it is beneficial to also add logged in email/account to the user sign up page as well to prevent possible confusion.
The text was updated successfully, but these errors were encountered: