30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
# 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, making sure to point to a valid path for where you are going to generate your RSA keypair.
|
|
|
|
Third, run `go build`.
|
|
|
|
Fourth, generate a RSA keypair using
|
|
`openssl genpkey -algorithm RSA -out private.pem -pkeyopt rsa_keygen_bits:2048`
|
|
`openssl rsa -pubout -in private.pem -out public.pem`
|
|
|
|
Fifth, 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.
|