Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oauth2: Not possible to link existing account #8923

Closed
2 of 8 tasks
Shuro opened this issue Nov 11, 2019 · 4 comments
Closed
2 of 8 tasks

Oauth2: Not possible to link existing account #8923

Shuro opened this issue Nov 11, 2019 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug

Comments

@Shuro
Copy link

Shuro commented 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

@BaxAndrei
Copy link

BaxAndrei commented Nov 19, 2019

I have same problem.

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

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 19, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jan 19, 2020
@stale stale bot removed the issue/stale label Jan 19, 2020
@SkYNewZ
Copy link

SkYNewZ commented 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 #9066

@zeripath
Copy link
Contributor

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

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

No branches or pull requests

5 participants