The service allows to verify query proofs. The private endpoints must be available only inside your backend system. Only one proof is stored per one user_id. If you request verification links second time for the same user_id, previous proof will be deleted. Think of it as a proxy server between your system and the mobile app.
Light verification is deprecated. See also integration doc.
git clone github.com/rarimo/verificator-svc
cd verificator-svc
go build main.go
export KV_VIPER_FILE=./config.yaml
./main migrate up
./main run service
You must specify following parameters before run the service:
- event_id - random decimal (up to 31 byte)
- callback_url - domain of your instance of the service
- allowed_identity_timestamp - date of your first production launch
We do use openapi:json standard for API. We use swagger for documenting our API.
To open online documentation, go to swagger editor here is how you can start it
cd docs
npm install
npm start
To build documentation use npm run build command,
that will create open-api documentation in web_deploy folder.
To generate resources for Go models run ./generate.sh script in root folder.
use ./generate.sh --help to see all available options.
Note: if you are using Gitlab for building project docs/spec/paths folder must not be
empty, otherwise only Build and Publish job will be passed.
Make sure that docker installed.
use docker run with -p 8080:80 to expose port 80 to 8080
docker build -t github.com/rarimo/verificator-svc .
docker run -e KV_VIPER_FILE=/config.yaml github.com/rarimo/verificator-svc
- Set up environment value with config file path
KV_VIPER_FILE=./config.yaml - Provide valid config file
- Launch the service with
migrate upcommand to create database schema - Launch the service with
run servicecommand
For services, we do use PostgresSQL database. You can install it locally or use docker image.
Responsible The primary contact for this project is [//]: # (TODO: place link to your telegram and email)