"Log in with Codeberg" #592

Open
opened 3 months ago by circlebuilder · 5 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.
Collaborator

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.
Poster

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.
Collaborator

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
Collaborator

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.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.