Codeberg/Community
54
325
Fork
You've already forked Community
12

How to see status of account linkage to (e.g.) github? #2083

Open
opened 2025年08月13日 13:57:43 +02:00 by lars_uffmann · 4 comments

Comment

I just linked my github account to my Codeberg one by using the "login via github" functionality, followed by approving (on github) the OAuth request from Codeberg, then logging into Codeberg again with my local credentials.
Is there a way (without actually migrating a github repo) to see the linked github account somewhere in my Codeberg profile information?

### Comment I just linked my github account to my Codeberg one by using the "login via github" functionality, followed by approving (on github) the OAuth request from Codeberg, then logging into Codeberg again with my local credentials. Is there a way (without actually migrating a github repo) to see the linked github account somewhere in my Codeberg profile information?

Hi, I cannot confirm this on my end as I do not own a GitHub account but I suspect it will be listed in some way or another under /user/settings/security -> linked accounts.

Hi, I cannot confirm this on my end as I do not own a GitHub account but I suspect it will be listed in some way or another under `/user/settings/security` -> linked accounts.

Thank you! I did not see that. However, there's a key piece of information missing from that:

Linked accounts
These external accounts are linked to your Forgejo account.
github Active

It does not show the name/id of the linked account, for tests and/or people who have multiple github accounts.

Thank you! I did not see that. However, there's a key piece of information missing from that: > Linked accounts > These external accounts are linked to your Forgejo account. > github Active It does not show the name/id of the linked account, for tests and/or people who have multiple github accounts.

Yeah such information doesn't seem to be passed at this moment. AFAIK there would not be another place where it would be, so I think we're looking at a new feature for Forgejo here?

Relevant code:

accountLinks,err:=db.Find[user_model.ExternalLoginUser](ctx,user_model.FindExternalUserOptions{
UserID:ctx.Doer.ID,
OrderBy:"login_source_id DESC",
})
iferr!=nil{
ctx.ServerError("ListAccountLinks",err)
return
}
// map the provider display name with the AuthSource
sources:=make(map[*auth_model.Source]string)
for_,externalAccount:=rangeaccountLinks{
ifauthSource,err:=auth_model.GetSourceByID(ctx,externalAccount.LoginSourceID);err==nil{
varproviderDisplayNamestring
typeDisplayNamedinterface{
DisplayName()string
}
typeNamedinterface{
Name()string
}
ifdisplayNamed,ok:=authSource.Cfg.(DisplayNamed);ok{
providerDisplayName=displayNamed.DisplayName()
}elseifnamed,ok:=authSource.Cfg.(Named);ok{
providerDisplayName=named.Name()
}else{
providerDisplayName=authSource.Name
}
sources[authSource]=providerDisplayName
}
}
ctx.Data["AccountLinks"]=sources
Yeah such information doesn't seem to be passed at this moment. AFAIK there would not be another place where it would be, so I think we're looking at a new feature for Forgejo here? Relevant code: https://codeberg.org/forgejo/forgejo/src/commit/c922ac5f3809f5b1b6730e14bdb06290e1dbe61b/routers/web/user/setting/security/security.go#L79-L112

Thank you for digging that up - I don't speak Go, so I can't really assess how much effort such a feature is, but I could imagine a tiny added providerUserName = <...> would be enough, and then include providerUserName in the generated HTML? So - like... two lines of code?

My main reason for not opening feature requests atm is that it seems there's way too much open work and I don't want to stress the devs out...

Thank you for digging that up - I don't speak Go, so I can't really assess how much effort such a feature is, but I could imagine a tiny added providerUserName = <...> would be enough, and then include providerUserName in the generated HTML? So - like... two lines of code? My main reason for not opening feature requests atm is that it seems there's way too much open work and I don't want to stress the devs out...
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
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.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
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.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2083
Reference in a new issue
Codeberg/Community
No description provided.
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?