github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Is it possible to choose default auth source? #3682

New Issue
Closed
opened 2025-11-02 05:21:33 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 05:21:33 -06:00
Owner
Copy Link

Originally created by @andloh on GitHub (Jul 26, 2019).

  • Gitea version (or commit ref): 1.10.0+dev-60-gc5f9c0418
  • Git version:
  • Operating system: linux
  • Database (use [x]):
    • [ x] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [x ] Not relevant
Originally created by @andloh on GitHub (Jul 26, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.10.0+dev-60-gc5f9c0418 - Git version: - Operating system: linux - Database (use `[x]`): - [ x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x ] Not relevant
GiteaMirror added the type/proposalissue/confirmed labels 2025-11-02 05:21:33 -06:00
GiteaMirror commented 2025-11-02 05:21:34 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jul 27, 2019):

How do you mean default? They all work at the same time

@lafriks commented on GitHub (Jul 27, 2019): How do you mean default? They all work at the same time
GiteaMirror commented 2025-11-02 05:21:34 -06:00
Author
Owner
Copy Link

@andloh commented on GitHub (Jul 27, 2019):

Thanks for answering
More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one.

@andloh commented on GitHub (Jul 27, 2019): Thanks for answering More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one.
GiteaMirror commented 2025-11-02 05:21:35 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 25, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 25, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 05:21:35 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 30, 2019):

@andloh Gitea support LDAP/mail/OAuth2 and etc. Is that what you mean?

@lunny commented on GitHub (Sep 30, 2019): @andloh Gitea support LDAP/mail/OAuth2 and etc. Is that what you mean?
GiteaMirror commented 2025-11-02 05:21:35 -06:00
Author
Owner
Copy Link

@andloh commented on GitHub (Sep 30, 2019):

No. The auth support is great. But i would like to disable some of them. So that users only have one auth source to interact with on the login page

@andloh commented on GitHub (Sep 30, 2019): No. The auth support is great. But i would like to disable some of them. So that users only have one auth source to interact with on the login page
GiteaMirror commented 2025-11-02 05:21:35 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Nov 29, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 29, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 05:21:36 -06:00
Author
Owner
Copy Link

@army1349 commented on GitHub (Oct 11, 2020):

Once role mapping is possible option to force OAuth2 auth source would be nice.

@army1349 commented on GitHub (Oct 11, 2020): Once [role mapping](https://github.com/go-gitea/gitea/issues/12493) is possible option to force OAuth2 auth source would be nice.
GiteaMirror commented 2025-11-02 05:21:36 -06:00
Author
Owner
Copy Link

@ailox commented on GitHub (Feb 21, 2021):

In addition to what @army1349 said, OIDC/OAuth2 Autoregistration (worked on in https://github.com/go-gitea/gitea/pull/5123) would also be useful to make login for existing OIDC accounts seamless.

@ailox commented on GitHub (Feb 21, 2021): In addition to what @army1349 said, OIDC/OAuth2 Autoregistration (worked on in https://github.com/go-gitea/gitea/pull/5123) would also be useful to make login for existing OIDC accounts seamless.
GiteaMirror commented 2025-11-02 05:21:36 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Aug 12, 2021):

I support this issue.

@tacerus commented on GitHub (Aug 12, 2021): I support this issue.
GiteaMirror commented 2025-11-02 05:21:36 -06:00
Author
Owner
Copy Link

@tacerus commented on GitHub (Sep 6, 2021):

I worked around this by adding a redirect to Gitea's oauth URL in my webserver (nginx) in order to directly forward users to our OIDC/SSO logon page upon clicking "Sign in" in Gitea - maybe it helps others:

location                /user/login {
return                  302 https://git.com.de/user/oauth2/LibertaCasaSSO;
}

The last bit is the name of the authentication provider that was set in Gitea - best to just visit the Gitea sign-in page regularly, right-clicking on the SSO/OIDC button, and selecting the browsers "Copy Link" option.

Note of course that this will make local logins impossible.

@tacerus commented on GitHub (Sep 6, 2021): I worked around this by adding a redirect to Gitea's oauth URL in my webserver (nginx) in order to directly forward users to our OIDC/SSO logon page upon clicking "Sign in" in Gitea - maybe it helps others: ``` location /user/login { return 302 https://git.com.de/user/oauth2/LibertaCasaSSO; } ``` The last bit is the name of the authentication provider that was set in Gitea - best to just visit the Gitea sign-in page regularly, right-clicking on the SSO/OIDC button, and selecting the browsers "Copy Link" option. Note of course that this will make local logins impossible.
GiteaMirror commented 2025-11-02 05:21:36 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 1, 2024):

Thanks for answering More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one.

The same request as #13606, will be implemented by #32687

@wxiaoguang commented on GitHub (Dec 1, 2024): > Thanks for answering More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one. The same request as #13606, will be implemented by #32687
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3682
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?