-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Summary] Improve auth source / login system #24821
Comments
Ideas to consider:
|
I think a good first step to this would be to only show username/email field on login page for first render, so flow sort of looks like this:
A good example of this would be https://accounts.zoho.com/signin. What do others think? |
In case of reverse proxy auth/header auth/certificate auth no login form is used and should not be rendered nor available. |
Feature Description
There are more and more requirements for a better login system.
Including (but not only):
Some of them might be improved by a "patch", but Gitea really needs a better login system to satisfies most users, otherwise some changes may conflict and block each other eventually.
The first step IMO is to have a (nearly) complete design,to define the expected behaviors for various situations.
Screenshots
No response
The text was updated successfully, but these errors were encountered: