A user management microservice; OAuth 2 provider
Space (formely known as Jupiter) is an user authentication and authorisation microservice intended to be used across multiple client applications. Currently, it's used to provide OAuth 2 authorisation for the earaujoassis/wallet and earaujoassis/postal projects. Though it is not intended to be used widely, it can be used as a reference implementation of a Go-based OAuth 2 provider.
It uses Gin as the Web Framework and GORM for Go's structure–relational mapping. Redis is used as a memory store to keep track of users' atomic and ephemeral actions (like the whole authorisation process under the "Authorization Code Grant" method, described in RFC 6749, section 4.1). For the user's authentication process, it is mandatory to use Two-factor authentication (Time-based One-time Password).
Additionally, the application supports the use of Hashicorp's Vault in order to obtain configuration information and secrets. It is planned to use Vault as a way to store clients keys and secrets, if the OAuth client application supports it.
It is not planned to implement all authorisation methods described in RFC 6749 but sections 4.1 and 4.3, the "Resource Owner Password Credentials Grant".
Space is based on a set of feature flags enabled/disabled through the Redis store.
Setup & running
Space is build on top of Golang and Node.js; both are manageable on top of
.tool-versions file is already provided. Space also uses Redis and Postgres as data stores – and optionally Vault.
Please make sure to place this project inside the
$GOPATH (a symbolic link could solve this or
simply go getting this like
$ go get github.com/earaujoassis/space) or to set the
GO111MODULE=on env var. A
file is used to load environment information for the application –
.env is already available. The application
PORT env var in order to setup its socket (it is automatically provided by
In order to setup the application, additional configuration is necessary. That could be delivered through Vault or through
.config.local.json file. If you plan to use Vault, you need to fill the
.config.yml file, according to the
.config.sample.yml, and store a k/v secret according to the
.config.local.sample.json. If don't plan to use Vault,
just create a
.config.local.json file according to
.config.local.sample.json. The application will try to load the
.config.local.json by default, if it is available; otherwise, it will attempt to load it from Vault. At least one of these
configuration schemes is necessary.
Once the configuration is complete, the following commands will run the server application locally:
$ yarn install && yarn build $ go get github.com/mattn/goreman $ goreman start $ open http://localhost:8080
If you're planning to setup it for development, ideally you should run:
$ bin/dev-setup $ go get github.com/mattn/goreman $ goreman start $ open http://localhost:8080
Testing & Linting
For testing (plus code coverage) and linting, you could run:
$ go get -u golang.org/x/lint/golint $ SPACE_ENV=testing go test -race -coverprofile=c.out ./... $ go tool cover -html=c.out -o coverage.html $ golint ./...
Deployment through a docker container
The following commands will create a docker image and create a docker container:
$ docker build -t earaujoassis/space . $ docker run -d -p 8080:8080 earaujoassis/space $ docker images --quiet --filter=dangling=true | xargs docker rmi
The project also provides a docker-compose setup, which could be setup through:
$ docker-compose up --build
If you have any question, comment or an issue, please take a look at /issues.
MIT License © Ewerton Carlos Assis