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

Two Factor not working after Account is linked with a Oauth2 login #1787

New Issue
Closed
opened 2025-11-02 04:13:14 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 04:13:14 -06:00
Owner
Copy Link

Originally created by @pree on GitHub (May 15, 2018).

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

Description

I had two factor authentication enabled on my account. Added a Oauth2 provider and linked my Oauth2 account with my gitea user. After the account was linked the two factor authentication does not work anymore. Even if I log in with Username/Password.
...

Screenshots

image

Originally created by @pree on GitHub (May 15, 2018). - Gitea version (or commit ref): 1.1.0+1201-g0b718e0d - Git version: - Operating system: Debian - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description I had two factor authentication enabled on my account. Added a Oauth2 provider and linked my Oauth2 account with my gitea user. After the account was linked the two factor authentication does not work anymore. Even if I log in with Username/Password. ... ## Screenshots ![image](https://user-images.githubusercontent.com/9799276/40080353-f5f4bd08-588a-11e8-934d-58d11b0b1374.png)
GiteaMirror added the type/bugissue/duplicate labels 2025-11-02 04:13:14 -06:00
GiteaMirror commented 2025-11-02 04:13:15 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (May 15, 2018):

@pree It's hard to diagnose the issue without further information. Can you please provide the log entries from that moment?

@daviian commented on GitHub (May 15, 2018): @pree It's hard to diagnose the issue without further information. Can you please provide the log entries from that moment?
GiteaMirror commented 2025-11-02 04:13:15 -06:00
Author
Owner
Copy Link

@pree commented on GitHub (May 24, 2018):

Hello daviian.
I will take a look at my logs later today to see if anything is reported there.

If you wan't to reproduce this, you could do this with the following steps:

  • Create User
  • Enable 2FA
  • Add an OAuth2 (OIC) Connection
  • Log into git via OAuth2
  • Merge the Accounts

After the merge the login isn't possible with this user.

@pree commented on GitHub (May 24, 2018): Hello daviian. I will take a look at my logs later today to see if anything is reported there. If you wan't to reproduce this, you could do this with the following steps: * Create User * Enable 2FA * Add an OAuth2 (OIC) Connection * Log into git via OAuth2 * Merge the Accounts After the merge the login isn't possible with this user.
GiteaMirror commented 2025-11-02 04:13:15 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 28, 2018):

Closed as dupe of #1509. Please re-open if you think it is different.

@techknowlogick commented on GitHub (Jun 28, 2018): Closed as dupe of #1509. Please re-open if you think it is different.
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/duplicate type/bug
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#1787
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?