Integrate an OAuth2 consumer #13

New Issue

GiteaMirror · 2025-11-02T03:03:31-06:00

GiteaMirror commented

2025-11-02 03:03:31 -06:00

Originally created by @tboerger on GitHub (Nov 3, 2016).

To keep the barrier of Gitea as small as possible we should integrate an OAuth2 consumer. That way new users can register with just a few clicks and can reuse there already elsewhere existing accounts. A good library for that can be https://github.com/markbates/goth.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @tboerger on GitHub (Nov 3, 2016). To keep the barrier of Gitea as small as possible we should integrate an OAuth2 consumer. That way new users can register with just a few clicks and can reuse there already elsewhere existing accounts. A good library for that can be https://github.com/markbates/goth. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39078610-integrate-an-oauth2-consumer?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the type/feature label 2025-11-02 03:03:31 -06:00

GiteaMirror closed this issue

2025-11-02 03:03:31 -06:00

GiteaMirror commented

2025-11-02 03:03:31 -06:00

@bkcsoft commented on GitHub (Jan 9, 2017):

oauth for searchabilty

( GitHub fix your search-engine FFS 😒 )

@bkcsoft commented on GitHub (Jan 9, 2017): oauth for searchabilty ( GitHub fix your search-engine FFS 😒 )

GiteaMirror commented

2025-11-02 03:03:31 -06:00

@willemvd commented on GitHub (Jan 9, 2017):

This would mean some area in the admin panel/app.ini to setup OAuth2 client_id, client_secret and a provider based on the goth provider list

Do we want to support non-existing goth providers (like MS ADFS/Office365) and let users enter a custom token & authorize url which we then can use to either create a new goth provider (not sure how) or use the golang.org/x/oauth2 package?

@willemvd commented on GitHub (Jan 9, 2017): This would mean some area in the admin panel/app.ini to setup OAuth2 client_id, client_secret and a provider based on the goth provider list Do we want to support non-existing goth providers (like MS ADFS/Office365) and let users enter a custom token & authorize url which we then can use to either create a new goth provider (not sure how) or use the golang.org/x/oauth2 package?

GiteaMirror commented

2025-11-02 03:03:31 -06:00

@tboerger commented on GitHub (Jan 10, 2017):

I think on the first step we will support the goth providers, but on another step we should also try to support more providers.

@tboerger commented on GitHub (Jan 10, 2017): I think on the first step we will support the goth providers, but on another step we should also try to support more providers.

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@lunny commented on GitHub (Feb 22, 2017):

So this has been resolved by #679 ?

@lunny commented on GitHub (Feb 22, 2017): So this has been resolved by #679 ?

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@willemvd commented on GitHub (Feb 22, 2017):

it will be broken in to multiple PR's, first part is in #679 , but I don't think we need this as reference for the other PR's

@willemvd commented on GitHub (Feb 22, 2017): it will be broken in to multiple PR's, first part is in #679 , but I don't think we need this as reference for the other PR's

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@lunny commented on GitHub (Feb 22, 2017):

So let's close this.

@lunny commented on GitHub (Feb 22, 2017): So let's close this.

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@Lichtjaeger commented on GitHub (Mar 13, 2017):

Nice work. But I would like to use Gitea on our intranet with our own OAuth2 provider (self-made with NodeJS).

I hope, this is planned for the next releases.

@Lichtjaeger commented on GitHub (Mar 13, 2017): Nice work. But I would like to use Gitea on our intranet with our own OAuth2 provider (self-made with NodeJS). I hope, this is planned for the next releases.

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@laf0rge commented on GitHub (Jun 4, 2019):

I also have several use cases (even on the public inthernet) where I'd want to be able to provide my own OAuth provider. Particularly privacy-sensitive users would not typically like to share too much data with the large Oauth "providers". So I think it's quite desirable for every entity/organization to run their own OAuth provider and not just rely on the big OAuth providers.

@laf0rge commented on GitHub (Jun 4, 2019): I also have several use cases (even on the public inthernet) where I'd want to be able to provide my own OAuth provider. Particularly privacy-sensitive users would not typically like to share too much data with the large Oauth "providers". So I think it's quite desirable for every entity/organization to run their own OAuth provider and not just rely on the big OAuth providers.

GiteaMirror commented

2025-11-02 03:03:32 -06:00

@lunny commented on GitHub (Jun 5, 2019):

I think you mean a customize OAuth2 config UI? @Lichtjaeger @lafOrge Maybe we could create another issue to discuss that.

@lunny commented on GitHub (Jun 5, 2019): I think you mean a customize OAuth2 config UI? @Lichtjaeger @lafOrge Maybe we could create another issue to discuss that.

GiteaMirror commented

2025-11-02 03:03:33 -06:00

@bryanpedini commented on GitHub (Jun 16, 2019):

I think you mean a customize OAuth2 config UI? @Lichtjaeger @laforge Maybe we could create another issue to discuss that.

Just crossing around open / solved issues of Gitea to better understand the underlying golang structure...
Immediately noticed you menti@ned the wrong user, @lunny, that 'o' was a zero..

@bryanpedini commented on GitHub (Jun 16, 2019): > > > I think you mean a customize OAuth2 config UI? @Lichtjaeger @laforge Maybe we could create another issue to discuss that. Just crossing around open / solved issues of Gitea to better understand the underlying golang structure... Immediately noticed you menti@ned the wrong user, @lunny, that 'o' was a zero..

GiteaMirror commented

2025-11-02 03:03:33 -06:00

@lunny commented on GitHub (Jun 16, 2019):

@Bryanpedini You are right. Sorry, @laf0rge

@lunny commented on GitHub (Jun 16, 2019): @Bryanpedini You are right. Sorry, @laf0rge

GiteaMirror commented

2025-11-02 03:03:33 -06:00

@Lichtjaeger commented on GitHub (Jun 17, 2019):

@lunny @laf0rge
This feature request has long been fulfilled. I'm using Gitea with our own auth server successfully for over a year now.

@Lichtjaeger commented on GitHub (Jun 17, 2019): @lunny @laf0rge This feature request has long been fulfilled. I'm using Gitea with our own auth server successfully for over a year now. ![grafik](https://user-images.githubusercontent.com/8598542/59580375-2d0e7e80-90d1-11e9-8371-691260bcc168.png) ![grafik](https://user-images.githubusercontent.com/8598542/59580429-5f1fe080-90d1-11e9-9204-ed2ae20368f3.png)

GiteaMirror referenced this issue

2025-11-02 11:53:12 -06:00

[PR #1040] [MERGED] Fix 500 when use a duplicate email instead of giving an error tip #15726

GiteaMirror referenced this issue

2025-11-02 11:53:13 -06:00

[PR #1042] [MERGED] Fix creating repo and register failed when duplicated email address. #15727

Sign in to join this conversation.