The Burgerauth authentication system, fully OAuth2 compatible!

Go to file

Tracker-Friendly f29a4de59c Debian compatiblity via older go version		2024-06-28 19:35:36 +01:00
static	Some extra padding and a confirmation dialouge	2024-05-18 00:51:36 +01:00
templates	Add the small 5px padding in main.html for the account button	2024-06-21 19:32:53 +01:00
.gitignore	Updated gitignore, fixed openid uri	2024-05-04 17:41:43 +01:00
ERRORS.md	Add ERRORS.md	2024-06-25 23:57:17 +01:00
LICENSE.md	Open source and release to the public	2024-04-26 20:12:56 +00:00
README.md	Joke added	2024-06-26 00:05:10 +01:00
go.mod	Debian compatiblity via older go version	2024-06-28 19:35:36 +01:00
go.sum	CAPTCHA support	2024-05-09 17:27:47 +01:00
main.go	Fixed silly error in checkusernametaken	2024-06-25 16:29:40 +01:00
schema.sql	Update the schema as well	2024-06-25 01:33:18 +01:00

README.md

Burgerauth

Burgerauth is a free-and-open-source OAuth2/OIDC (or as I've taken to calling it, OAuth2 + OIDC) server.

Ok, that's great, how do I host my own instance?

First, replace the domains in the source code and templates with your own (a domain is required, not just an IP). Second, copy config.ini.example to config.ini then tweak to your liking. Third, run go build, and fourth, run ./burgerauth. Read ERRORS.md to see how to handle server errors.

What if I am a developer?

The OAuth2 protocol should be fairly standard. Burgerauth comes with OpenID Connect discovery, and you should use that to find out the URL endpoints for the instance you are targeting, and you shouldn't really touch anything else. Burgerauth provides only authorization and not resource-delegation, and so doesn't issue refresh tokens.

How long did this take to make?

Yes.

What do you mean "OAuth2 + OIDC"?

OIDC is not a protocol in of itself, but rather an extension on top of a fully working OAuth2 system, made useful by the OAuth2 protocol and JWK token protocol.