Skip to content

Gitea as an OpenID-2.0 provider #1310

Open
@strk

Description

@strk
Member

Now that OpenID instances can be configured to accept an OpenID login, it could be nice if they ccould also serve as OpenID providers so to build what would become the authentication layer of a federation of code repositories. See also #184

Activity

added this to the 1.x.x milestone on Mar 18, 2017
added
type/featureCompletely new functionality. Can only be merged if feature freeze is not active.
on Mar 18, 2017
cweiske

cweiske commented on Jul 14, 2017

@cweiske
jhasse

jhasse commented on Jul 14, 2017

@jhasse

It isn't necessary, but it makes it easier as you don't have to create a traditional account on every Gitea instance where you want to open a pull request (and you don't have or don't want to use a different OpenID provider).

bkcsoft

bkcsoft commented on Aug 24, 2017

@bkcsoft
MaxG87

MaxG87 commented on Feb 11, 2019

@MaxG87

Albeit this thread is quiet for some time I want to add some points for the sake of the argument.

If you can setup your own gitea-instance you can setup your own OpenID provider.

And instantly you have to maintain two systems instead of one. Because a project decided not to contribute to infrastructure it partly relies on. And maintaining more systems in a self-hosting setting means much more opportunity to miss important updates.

Furthermore, at least for me, the condition of free, decentralised OpenID infrastructure seems to be quite bad. You can reuse the logins of your accounts at the usual tech giants, but only because someone hardcoded the support for them. I hardly know a service where you can use OpenID tokens from the provider of your choice. I also don't know providers of such tokens that could be used freely. All I know off is the possibility to integrate third-party-logins in your website for preselected third parties.

Long story short: OpenID needs more providers, otherwise Giteas OpenID feature cannot be used in a decentralised way. Gitea should be such a provider to reduce required mainenance efforts in self-hosting settings.

I really don't get why Gitea has to be a provider for everything

It is only about OpenID, isn't it? For me, this seems to be much less than everything.

lunny

lunny commented on Apr 21, 2019

@lunny
Member

Since Gitea now could be as OAuth2 provider, that's not too difficult.

stale

stale commented on Jun 20, 2019

@stale

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

added
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implemented
on Jun 20, 2019
strk

strk commented on Jun 20, 2019

@strk
MemberAuthor

I still think this is an important feature. Since Gitea does support OpenID-2.0, by acting as a provider would allow accessing all enabled Gitea instances via identity provided by your own. A big step toward federation.

zeripath

zeripath commented on Jun 20, 2019

@zeripath
Contributor

If you put links to the specs in this issue anyone that's interested in building this functionality will have an easier time doing it.

6543

6543 commented on Nov 6, 2019

@6543
Member

gitea now can act as openID provider - so close this issue?

17 remaining items

strk

strk commented on Jun 28, 2021

@strk
MemberAuthor

Why was this closed ? There's no discovery implemented.

reopened this on Jun 28, 2021
changed the title [-]Gitea as an OpenID provider[/-] [+]Gitea as an OpenID-2.0 provider[/+] on Jun 28, 2021
strk

strk commented on Jun 28, 2021

@strk
MemberAuthor

But that's for oath, not OpenID-2.0, right ?

6543

6543 commented on Jun 28, 2021

@6543
Member

hmm I thought it is for OpenID, to auto-discover things ...

cweiske

cweiske commented on Jun 28, 2021

@cweiske
Contributor

That is OpenID connect. OpenID 2 is something completely different :(

removed this from the 1.x.x milestone on Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtopic/authenticationtopic/federationtype/featureCompletely new functionality. Can only be merged if feature freeze is not active.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @philpraxis@cweiske@jhasse@lunny@strk

      Issue actions

        Gitea as an OpenID-2.0 provider · Issue #1310 · go-gitea/gitea