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

Oauth2: Not possible to link existing account #4285

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

Originally created by @Shuro on GitHub (Nov 11, 2019).

  • Gitea version (or commit ref): 1.11.0+dev-210-g74bb292fe (docker / latest)
  • Git version: 2.22.0
  • Operating system: Vmware PhotonOS (docker)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
    • not possible
  • Log gist:

Description

I migrated my gitea installation to the docker gitea instance, everything works fine so far, except logging in via google Oauth2.

Steps to reproduce:

  1. Visit oauth2 login path: https://git.domain.tld/user/oauth2/Google
  2. log in with google account
  3. redirect back to https://git.domain.tld/user/link_account#
  4. switch to "Link to Existing Account"
  5. Type in Username and press enter

Expected behavior:

  • get asked for user password
  • login
  • oauth2 account bound

Actual behavior:

  • Landing again on https://git.domain.tld/user/link_account# , register tab
  • switch to "Link to Existing Account" reveals the error: "Password cannot be empty."
  • there was and is no password field (see attached screenshot)

Screenshots

Bildschirmfoto_2019-11-11_15-29-49

Originally created by @Shuro on GitHub (Nov 11, 2019). - Gitea version (or commit ref): 1.11.0+dev-210-g74bb292fe (docker / latest) - Git version: 2.22.0 - Operating system: Vmware PhotonOS (docker) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - [x] not possible - Log gist: ## Description I migrated my gitea installation to the docker gitea instance, everything works fine so far, except logging in via google Oauth2. ## Steps to reproduce: 1. Visit oauth2 login path: https://git.domain.tld/user/oauth2/Google 2. log in with google account 3. redirect back to https://git.domain.tld/user/link_account# 4. switch to "Link to Existing Account" 5. Type in Username and press enter ### Expected behavior: - get asked for user password - login - oauth2 account bound ### Actual behavior: - Landing again on https://git.domain.tld/user/link_account# , register tab - switch to "Link to Existing Account" reveals the error: "Password cannot be empty." - there was and is no password field (see attached screenshot) ## Screenshots ![Bildschirmfoto_2019-11-11_15-29-49](https://user-images.githubusercontent.com/944030/68595255-60dfab80-0499-11ea-9ca8-cd07ed44353a.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:44:49 -06:00
GiteaMirror commented 2025-11-02 05:44:50 -06:00
Author
Owner
Copy Link

@BaxAndrei commented on GitHub (Nov 19, 2019):

I have same problem.

Gitea version (or commit ref): 1.10.0
Operating system: CentOS Linux release 7.7.1908

@BaxAndrei commented on GitHub (Nov 19, 2019): I have same problem. Gitea version (or commit ref): 1.10.0 Operating system: CentOS Linux release 7.7.1908
GiteaMirror commented 2025-11-02 05:44:50 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 19, 2020):

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 (Jan 19, 2020): 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:44:50 -06:00
Author
Owner
Copy Link

@SkYNewZ commented on GitHub (Jan 20, 2020):

Move to Gitea version 1.10.1 built with GNU Make 4.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify has fixed this issue for me https://github.com/go-gitea/gitea/issues/9066

@SkYNewZ commented on GitHub (Jan 20, 2020): Move to `Gitea version 1.10.1 built with GNU Make 4.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify` has fixed this issue for me https://github.com/go-gitea/gitea/issues/9066
GiteaMirror commented 2025-11-02 05:44:50 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jan 20, 2020):

Ok closing as fixed. Please reopen if still a problem.

@zeripath commented on GitHub (Jan 20, 2020): Ok closing as fixed. Please reopen if still a problem.
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/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#4285
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?