You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
jhasse, hlandau, mwyvr, Mikaela, dschmidt and 17 morecweiske, pojntfx and caesarMikaela, aschrijver, mawalu, pojntfx and xplosionmindxplosionmind
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).
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.
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.
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.
MaxG87, v-byte-cpu, philpraxis, aschrijver, pjanx and 2 more
Activity
cweiske commentedon Jul 14, 2017
jhasse commentedon Jul 14, 2017
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 commentedon Aug 24, 2017
MaxG87 commentedon Feb 11, 2019
Albeit this thread is quiet for some time I want to add some points for the sake of the argument.
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.
It is only about OpenID, isn't it? For me, this seems to be much less than everything.
lunny commentedon Apr 21, 2019
Since Gitea now could be as OAuth2 provider, that's not too difficult.
stale commentedon Jun 20, 2019
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.
strk commentedon Jun 20, 2019
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 commentedon Jun 20, 2019
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 commentedon Nov 6, 2019
gitea now can act as openID provider - so close this issue?
17 remaining items
strk commentedon Jun 28, 2021
Why was this closed ? There's no discovery implemented.
[-]Gitea as an OpenID provider[/-][+]Gitea as an OpenID-2.0 provider[/+]6543 commentedon Jun 28, 2021
@strk I think so: https://try.gitea.io/.well-known/openid-configuration
strk commentedon Jun 28, 2021
But that's for oath, not OpenID-2.0, right ?
6543 commentedon Jun 28, 2021
hmm I thought it is for OpenID, to auto-discover things ...
cweiske commentedon Jun 28, 2021
That is OpenID connect. OpenID 2 is something completely different :(