Support federated login for guest users (OpenID)

[stevenroose]

From @stevenroose on May 26, 2015 9:5

It bothers many that they have to enter a full form of personal information in order to just file a bug or make a feature request.
OpenID support can fix this and allows guest users to login with they GitHub of Google account f.e.

Ideally, it would also be possible to restrict these "guest"/external users to only be able to make create issues and pull requests and not have their own repositories.

Copied from original issue: gogs/gogs#1297

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39298589-support-federated-login-for-guest-users-openid?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).

[sbrl]

Waaaaat? I don't understand what's going on here. What's gitea? Why has it been forked? Is gogs still a thing?

To answer [this comment], I don't think I can since I don't have go installed, I don't know go, I don't understand the go package system, and I don't understand openid 😕 😞

???

[tboerger]

@stevenroose you shouldn't copy everything, a single reference to the issue should be fine.

[strk]

@sbrl gitea is a fork of gogs made to avoid development being blocked by a single person in charge of accepting contributions. Management of gitea is in the hands of 3 owners elected yearly by a growing number of maintainers (currently 10). See the CONTRIBUTING.md file for further details.

Binary packages, for those who don't want to build from sources, are in the works, see #31

[sbrl]

Ah right! I might switch when a full release is made then.

[bkcsoft]

@tboerger One can always clean it up 😉 (Like I just did)

[tscs37]

I'm in favor of adding basic OpenID support and like to also propose OpenID Connect support.

That would allow arbitrary federation from any provider that supports OpenID Connect.

[strk]

@tscs37 are you up to try at moving some steps toward the implementation of one or the other ?
I've moved the first step for OpenID but it's far from ready (mostly needs UX design), see #271

As per OpenID Connect, do you know of any consumer implementation that does support arbitrary provider support ? I'm asking because I don't and would like to spread the word about its existance.

[stevenroose]

@strk StackExchange has it (prob not open source). I thought the OSQA had it too, that's an old open-source clone of SE. Or is that basic OpenID?

[strk]

I can log into StackExchange with my OpenID-2.0 provider (not OAuth based). I dont' have an OpenID-Connect provider to test with StackExchange, but I suspect only hard-coded providers would be supported there.

[stevenroose]

Just to copy from @strk 's PR:

The big advantage I would see from having OpenID is as a way of users to login without having been registered. Just like systems like Discuss allow anyone with an OpenID (even though Discuss requires this to be from a small set of providers) to make contributions in the form of issues or (federated) pull requests.

A possible setup that would benefit greatly from OpenID is the case of single-user usage. Gitea as a self-hosted Git homepage in which only one user has commit access, while he can allow anyone to open issues or request pulls with their OpenID (and a CAPTCHA ofc).