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

Prefer making OAuth2 logins visible #2198

Open
opened 2025年11月04日 21:26:01 +01:00 by kcuasay · 1 comment

Description

Currently, Codeberg supports GitHub and GitLab as IdPs, which makes creating an account for the user an easy, and, arguably, more secure experience. However, those IdPs are hidden and are only revealed after expanding the Sign in with ... drop down. Taking a glance at the relevant template and at commit Codeberg-Infrastructure/forgejo@79c18820b4, it appears this is an intentional design choice. For the users who had noticed, this can come off as a bit strange, as IdPs are typically made visible to the user rather than hidden. While for the ones who did not notice and are signing up for the first time, it can feel a bit annoying for them because it would mean yet another username/password to manage and 2FA to enroll.

Therefore, I'm interested to know a bit of background on that design choice, and why IdPs are intentionally being discouraged to use as sign in options.

### Description Currently, Codeberg supports GitHub and GitLab as IdPs, which makes creating an account for the user an easy, and, arguably, more secure experience. However, those IdPs are hidden and are only revealed after expanding the `Sign in with ...` drop down. [Taking a glance at the relevant template](https://codeberg.org/Codeberg-Infrastructure/forgejo/src/commit/2d1ffdaaa49e99679ce31ba75c76a3b999c063c9/templates/user/auth/oauth_container.tmpl#L7) and at commit https://codeberg.org/Codeberg-Infrastructure/forgejo/commit/79c18820b44c90c58a700d5b1b021bca4920c972, it appears this is an _intentional_ design choice. For the users who had noticed, this can come off as a bit strange, as IdPs are typically made visible to the user rather than hidden. While for the ones who did _not_ notice and are signing up for the first time, it can feel a bit annoying for them because it would mean yet another username/password to manage and 2FA to enroll. Therefore, I'm interested to know a bit of background on that design choice, and why IdPs are intentionally being discouraged to use as sign in options.

As you noted this is a intentional choice, we do not wish to promote using Github or Gitlab accounts to login to Codeberg. You will be tied to their platforms when doing that. CC @fnetX in case you also have a perspective on this.

As you noted this is a intentional choice, we do not wish to promote using Github or Gitlab accounts to login to Codeberg. You will be tied to their platforms when doing that. CC @fnetX in case you also have a perspective on this.
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#2198
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?