WaTTS - the INDIGO Token Translation Service
Erlang Elm Python CSS Makefile Shell Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
config
docker
gitbook
include
priv/http_static
src
test
ui
utils keep tts package name, #306 Jan 12, 2017
.gitignore
LICENSE
Makefile
README.md
book.json
package.mk
pkg.vars.config
rebar.config
rebar.lock
rebar3

README.md

WaTTS - The INDIGO Token Translation Service

Purpose

WaTTS creates credentials for services that do not natively support OpenID Connect. Such services are for example ssh, S3 storage, OpenNebula or certificate authorities, CAs.

WaTTS creates credentials for these services by using plugins. Plugins are scripts that can be adapted by a site-administrator.

Quickstart

WaTTS requires Erlang OTP 18.1 or newer to run (due to a bug in the cover compiler OTP 18.3 or newer is needed to run the tests). For configuration WaTTS uses cuttlefish, which needs to be installed into the Erlang Runtime Sytem directory. Scripts to support you are in the utils directory of this repository.

First clone the repository and change into the cloned directory:

git clone https://github.com/indigo-dc/tts.git
cd tts

If you do not have Erlang installed and want a fast and easy setup run:

./utils/prepare_system.sh

This will install Erlang and cuttlefish onto you system.

Now copy the sample configuration and after that adjust it to your needs, the config will be at ~/.config/watts:

make sample_config

Once you are satisfied with your config or just to start TTS after some configuration changes:

make run

Now Browse to your local WaTTS on localhost:8080

If you want to stop WaTTS you just need to type the following in the console (the '.' at the end is important):

q().

The sample configuration includes a development INDIGO Idetntity and Access Management (IAM) configuration that only runs at localhost:8080 and a simple Info service.

Just edit the configuration file to add more OpenId Connect Provider or services. The steps needed to do this are described in the Configuration Guide

Documentation

Further documentation of WaTTS can be found at the WaTTS Documentation on GitBook.