this would make migration from GitHub/GitLab eaven easyer: user who have created an accounton Codeberg and linked this one with a GitHub account later, will automaticaly take over the ownership of issues/pulls/comments on repos witch had used the build-in Migration tool.
add GitHub and GitLab as Oauth2 sources #225
Personally I would like to support linking the account for issue/pulls/comments migration.
But I would like to do it without enabling "login/register with github". Accounts created that way behaved weird in our and tests by @davidak .
It that possible?
Accounts created that way behaved weird
Noticed too, there is somehow a diffrence if you create fia github or link an account afterwards - but didn't digged into this rabit hole jet
... posible without enabling ... github login ...
sadly: NO
this is the general problem of how to make sure that someone realy own the account X on platform Y
Noticed too, there is somehow a diffrence if you create fia github or link an account afterwards - but didn’t digged into this rabit hole jet
Yes, this is what I mean, I would like to disable "create via github" but keep "link account afterwards". A patch for gitea/codeberg would be neccessary I guess.
@ashimokawa if we like to get it with v1.12.x I think a patch will be needed :/
upstream issue: https://github.com/go-gitea/gitea/issues/12342
upstream pull: https://github.com/go-gitea/gitea/pull/15795
ok did we come to the conclusion it's working fine ...?
can be tested on https://codeberg-test.org/ atm :D
Think so, missing thing is some explanation in the docs on how to connect?
well thinks so,
jut the hint we have to make sure...:
- Github oauth authentification source has te be named
github - Gitlab oauth authentification source has te be named
gitlab
INFO: Codeberg/gitea@0d3874b691 will make it posible, on next deploy 🚀
I tried to test this and failed, maybe at the CAPTCHA. #483
This would help a lot to convince projects to migrate to codeberg as their users can still contribute easily with github/gitlab account.
I don't know if the login sources are setup properly yet or maybe broken? Testing this is highly appreciated before we rollout to prod, I'm not sure about the current state.
We'll hit this issue up as soon as we get to this topic again ...
It should work all fine?
What do you rever to @fnetX ?
It should work all fine?
have you tested it? shouldn't take too long
it fails for me
steps to reproduce:
- don't have an account on the test instance
- open https://codeberg-test.org/user/login
- click Sign In With GitHub
- the page "Link to Existing Account" (https://codeberg-test.org/user/link_account) opens
- i don't have an account, so i input random characters and click Link account
- then i get to the page https://codeberg-test.org/user/link_account_signin where i click the option Register New Account (i don't see it on the first site)
- i input my user name (davidak), e-mail und captcha and click "Complete Account"
- i get a white page with the text "Forbidden"
the browser console (Chromium 91.0.4472.114) says:
Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.
link_account_signup:1 POST https://codeberg-test.org/user/link_account_signup 403
here is a video that shows the issue and how it works on https://try.gitea.io/
https://peertube.social/videos/watch/eaf0278a-f14c-4018-83cc-0c2a3706dea6
Yeah this isn't the supposed workflow. It's not described, because it's not on prod yet.
You have to register an account first, then sign-in with GitHub and link it.
Maybe this can be changed, but it's not the way it's supposed to work.
It's at least a bug that you see the sign-up tab after entering non-working credentials ...
whats the point in "sign in with github" if i need to register locally anyway?
You can link your account with migrated content. The issues do not longer show some random GitHub user, but your account etc ...
If possible, I personally don't object to logging in with GitHub, but we had issues with having access to the users mail address IIRC ...
hmm https://codeberg-test.org/user/link_account_signin should return 404 or better redirect to normal signup
It works now to link an existing account.
Tested on https://codeberg-test.org/.
Would be great if one could create an account just from GitHub login. So UX would be:
- Click "Login with GitHub"
- Allow to use user data from GitHub
- You are logged in with your new account
It uses the e-mail github has and you can reset your password with that address if github would disappear.
@davidak another issue - "enable auto account creation on oauth login" ... ;)
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
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?