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

Possibility Of Login with Both Ldap and Open ID to same account #4097

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

Originally created by @kstan79 on GitHub (Oct 11, 2019).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • [x ] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [x ] Not relevant
  • Log gist:

Description

I wish to allow user to login via openid from web console, but clone checkout/push/etc using ldap password. The reason behind is we have internal keycloak server which bind to ldap.
At this moment, gitea require to maintain internal password when I bind account to openid server. I know there is alternative way like using certificate file but that is not preferable option due to it added complexity of deployment.

Screenshots

Originally created by @kstan79 on GitHub (Oct 11, 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): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [x ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x ] Not relevant - Log gist: ## Description I wish to allow user to login via openid from web console, but clone checkout/push/etc using ldap password. The reason behind is we have internal keycloak server which bind to ldap. At this moment, gitea require to maintain internal password when I bind account to openid server. I know there is alternative way like using certificate file but that is not preferable option due to it added complexity of deployment. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/confirmedtype/proposal labels 2025-11-02 05:37:44 -06:00
GiteaMirror commented 2025-11-02 05:37:45 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 10, 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 (Dec 10, 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:37:45 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Feb 20, 2020):

Sounds like a great idea, any chance you'll be able to think about how it could be implemented ?
Right now OpenID accounts are considered "local" so I guess we could switch from local to LDAP to do that. See also https://github.com/go-gitea/gitea/issues/1124 as I think it's somewhat related

@strk commented on GitHub (Feb 20, 2020): Sounds like a great idea, any chance you'll be able to think about how it could be implemented ? Right now OpenID accounts are considered "local" so I guess we could switch from local to LDAP to do that. See also https://github.com/go-gitea/gitea/issues/1124 as I think it's somewhat related
GiteaMirror commented 2025-11-02 05:37:46 -06:00
Author
Owner
Copy Link

@flortsch commented on GitHub (Jan 6, 2021):

For me, this actually works. In Gitea, I setup an LDAP backend (FreeIPA) and OpenID provider (Keycloak). I can login with LDAP information, and on first login with OpenID, I can link to the existing Gitea account from the LDAP backend. With this, both OpenID via browser and repo interactions on the terminal via LDAP login work.

@flortsch commented on GitHub (Jan 6, 2021): For me, this actually works. In Gitea, I setup an LDAP backend (FreeIPA) and OpenID provider (Keycloak). I can login with LDAP information, and on first login with OpenID, I can link to the existing Gitea account from the LDAP backend. With this, both OpenID via browser and repo interactions on the terminal via LDAP login work.
GiteaMirror commented 2025-11-02 05:37:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 14, 2021):

As @flortsch said, I will close this and please feel free to reopen it.

@lunny commented on GitHub (Jan 14, 2021): As @flortsch said, I will close this and please feel free to reopen it.
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#4097
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?