Codeberg/Community
60
387
Fork
You've already forked Community
12

"Log in with Codeberg" #592

Closed
opened 2022年03月07日 11:38:54 +01:00 by circlebuilder · 9 comments

There are so many apps and services that have a "Log in with Github" auth facility. They lower the barrier to sign up significantly. Codeberg might provide similar login facilities (OAuth / OIDC? I'm not an expert) and have a project where integrations are built and tracked.

Background:

I just installed a Discourse forum for a developer audience. I can enable Github login out-of-the-box, but since all code will be on Codeberg this feels a bit weird and also I want to promote usage of both Codeberg and Gitea as better alternatives than Github.

As for Discourse accounts.. they are most-used forum software I think for developer communities, and I am member of many forums. If they have their code on Github I usually reuse my Github account to login.

There are so many apps and services that have a "Log in with Github" auth facility. They lower the barrier to sign up significantly. Codeberg might provide similar login facilities (OAuth / OIDC? I'm not an expert) and have a project where integrations are built and tracked. **Background:** I just installed a Discourse forum for a developer audience. I can enable Github login out-of-the-box, but since all code will be on Codeberg this feels a bit weird and also I want to promote usage of both Codeberg and Gitea as better alternatives than Github. As for Discourse accounts.. they are most-used forum software I think for developer communities, and I am member of many forums. If they have their code on Github I usually reuse my Github account to login.
Owner
Copy link

Gitea already has an OAuth. For example, you can login to the Woodpecker CI with your Codeberg account (if you were granted access). And https://code.obermui.de/user/login has a login with Codeberg, too.

It's up to the external applications to implement the "Login with Gitea/Codeberg" feature. We can collect potential candidates here, but honestly I think the requests better fit their issue tracker. I doubt we will have time to take care of (m)any other projects.

Gitea already has an OAuth. For example, you can login to the Woodpecker CI with your Codeberg account (if you were granted access). And https://code.obermui.de/user/login has a login with Codeberg, too. It's up to the external applications to implement the "Login with Gitea/Codeberg" feature. We can collect potential candidates here, but honestly I think the requests better fit their issue tracker. I doubt we will have time to take care of (m)any other projects.

I understand. Besides handy I saw it more as a promotional feature for Codeberg. At Discourse the team is likely not very interested to offer a tailored 'Login with Codeberg'. But they are interested in Github because of its popularity.

The project bulding/tracking integrations would be crowdsourced. Not a task of Codeberg team to spend time on, but encourage Codeberg users to contribute to.

It is just an idea, though, and you might close if you don't think its a good issue for this tracker.

I understand. Besides handy I saw it more as a promotional feature for Codeberg. At Discourse the team is likely not very interested to offer a tailored 'Login with Codeberg'. But they are interested in Github because of its popularity. The project bulding/tracking integrations would be crowdsourced. Not a task of Codeberg team to spend time on, but encourage Codeberg users to contribute to. It is just an idea, though, and you might close if you don't think its a good issue for this tracker.

It's up to the external applications to implement the "Login with Gitea/Codeberg" feature. We can collect potential candidates here, but honestly I think the requests better fit their issue tracker. I doubt we will have time to take care of (m)any other projects.

I have not implemented OAuth yet and I dont know if it is straigtforwared but should we create a documentation section for that

> It's up to the external applications to implement the "Login with Gitea/Codeberg" feature. We can collect potential candidates here, but honestly I think the requests better fit their issue tracker. I doubt we will have time to take care of (m)any other projects. I have not implemented OAuth yet and I dont know if it is straigtforwared but should we create a documentation section for that
Owner
Copy link

There are probably better technical documentations on how to implement OAuth per tech stack. Otherwise, there are the specs. I don't see any reason to write our own "How To Oauth". There are thousands of apps that support OAuth, they can't each write their own OAuth guide just because they think someone might add OAuth support in third-party apps which can then connect to their app.

Regarding a crowdsourced list, this makes sense. If people say where they might want to see OAuth, we get an impression of the actual demand and people can then decide which app they pick if they are interested in implementing this somewhere.

There are probably better technical documentations on how to implement OAuth per tech stack. Otherwise, there are the specs. I don't see any reason to write our own "How To Oauth". There are thousands of apps that support OAuth, they can't each write their own OAuth guide just because they think someone might add OAuth support in third-party apps which can then connect to their app. Regarding a crowdsourced list, this makes sense. If people say where they might want to see OAuth, we get an impression of the actual demand and people can then decide which app they pick if they are interested in implementing this somewhere.

There are most likely better specialized documentations on the most proficient method to execute OAuth per tech stack. In any case, there are the specs. I see no good excuse to compose our own "How To Oauth". There are great many applications that help OAuth, they can't each compose their own OAuth guide since they figure somebody could add OAuth support in outsider applications which can then interface with their application.

There are most likely better specialized documentations on the most proficient method to execute OAuth per tech stack. In any case, there are the specs. I see no good excuse to compose our own "[How To Oauth](https://bestmachete.co/)". There are great many applications that help OAuth, they can't each compose their own OAuth guide since they figure somebody could add OAuth support in outsider applications which can then interface with their application.
Add CB to tailscale: https://github.com/tailscale/tailscale/issues/4717

For the record a related topic about weblate and sign-in from Codeberg.

For the record [a related topic about weblate](https://codeberg.org/Codeberg/Community/issues/463) and sign-in from Codeberg.

I would close this as duplicate to #463

as we only can document from our side, the other projects have to adapt it ... (ease for foss projects to do so ... hard for propritarian)

I would close this as duplicate to #463 as we only can document from our side, the other projects have to adapt it ... (ease for foss projects to do so ... hard for propritarian)

@6543 Please add duplicate label!

@6543 Please add `duplicate` label!
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 Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, 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
7 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#592
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?