Disable login by user / password but keep openId connect #5096

Closed
opened 2025-11-02 06:14:19 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @weeman1337 on GitHub (Mar 22, 2020).

  • Gitea version (or commit ref): 1.11.3

Description

I wonder if it's possible to remove the login fields but keep the "open id connect" login button.
Event better would be directly trying to authenticate via "open id connect".

I've played around with the config but had no luck so far.

Screenshots

image

Originally created by @weeman1337 on GitHub (Mar 22, 2020). - Gitea version (or commit ref): 1.11.3 ## Description I wonder if it's possible to remove the login fields but keep the "open id connect" login button. Event better would be directly trying to authenticate via "open id connect". I've played around with the config but had no luck so far. ## Screenshots ![image](https://user-images.githubusercontent.com/6216686/77249526-e6dae280-6c41-11ea-9cb3-651cad0e42bf.png)
GiteaMirror added the type/enhancementissue/stale labels 2025-11-02 06:14:19 -06:00
Author
Owner

@lunny commented on GitHub (Mar 22, 2020):

You can customerize the login page currently.

@lunny commented on GitHub (Mar 22, 2020): You can customerize the login page currently.
Author
Owner

@weeman1337 commented on GitHub (Mar 22, 2020):

Thanks for the fast response.

You can customerize the login page currently.

That means I should provide my own template for doing that?

Isn't it a valid use case for a centralized managed user base to provide an option to remove the login fields?

@weeman1337 commented on GitHub (Mar 22, 2020): Thanks for the fast response. > You can customerize the login page currently. That means I should provide my own template for doing that? Isn't it a valid use case for a centralized managed user base to provide an option to remove the login fields?
Author
Owner

@guillep2k commented on GitHub (Mar 25, 2020):

Isn't it a valid use case for a centralized managed user base to provide an option to remove the login fields?

@weeman1337 yes, it is, The template edit is a suggestion in case you need a workaround.

Maybe you can send a PR for this functionality? 😁

@guillep2k commented on GitHub (Mar 25, 2020): > Isn't it a valid use case for a centralized managed user base to provide an option to remove the login fields? @weeman1337 yes, it is, The template edit is a suggestion in case you need a workaround. Maybe you can send a PR for this functionality? 😁
Author
Owner

@stale[bot] commented on GitHub (May 25, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 25, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Jun 9, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 9, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5096