Turns your plaintext secret into a ciphertext encoded with a named key through the magic of vault's transit backend.

1. Get vault up and running (ACS currently has only been tested against vault 0.6.0)

   $ vault server -dev -dev-root-token-id="your-root-token"
   
   # In another terminal
   $ export VAULT_ADDR='http://127.0.0.1:8200'
   $ vault mount transit
   $ vault write -f transit/keys/your_acs_key

2. start tokend's metadata-server

   $ cd /path/to/tokend/ && npm run metadata-server

3. start tokend's warden-mock

   $ cd /path/to/tokend && npm run warden-mock -- your-root-token

4. start tokend

   $ cd /path/to/tokend && npm run dev

5. Start ACS

   $ cd /path/to/acs && npm run dev

6. Navigate to localhost:3000 in your browser

You specify a configuration file at run time like this: npm start -- -c path/to/your/config.json

Here is a full example of a config.json with all of the available configuration parameters:

{
  "vault": {
    "host": "127.0.0.1",
    "port": 8200,
    "tls": false,
    "transit_key": "your_acs_key"
  },
  "tokend": {
    "host": "localhost",
    "port": 4500,
    "path": "/v1/token/default"
  },
  "log": {
    "level": "INFO",
    "json": true,
    "requests": true
  },
  "service": {
    "host": "localhost",
    "port": 3000
  }
}