vts-service

README

Configuration

vts-services is expecting to find the following top-level entries in configuration:

• ta-store: trust anchor store configuration. See kvstore config.
• en-store: endorsements store configuration. See kvstore config.
• po-store: policy store configuration. See kvstore config.
• po-agent (optional): policy agent configuration. See policy config.
• plugin: plugin manager configuration. See plugin config.
• vts (optional): Veraison Trusted Services backend configuration. See trustedservices config.
• logging (optional): Logging configuration. See logging config.
• ear-signer: Attestation Result signing configuration. See signer config.

Config files

There are two config files in this directory:

• config.yaml is designed to be used when running vts-service directly form this directory. This is no longer supported (use the native deployment instead). It is kept for illustrative purposes only.
• config-docker.yaml this is the file that is designed to be used when running inside the debug docker container. See debugging docker deployment. The debug command inside the debug container will automatically use it. If running the executable directly, this file will need to be specified with --config option.

Example

ta-store:
  backend: sql
  sql:
    driver: sqlite3
    datasource: ta-store.sql
en-store:
  backend: sql
  sql:
    driver: sqlite3
    datasource: en-store.sql
po-store:
  backend: sql
  sql:
    driver: sqlite3
    datasource: po-store.sql
po-agent:
    backend: opa
plugin:
  backend: go-plugin
  go-plugin:
    folder: ../../plugins/bin/
vts:
  server-addr: 127.0.0.1:50051
ear-signer:
  alg: ES256
  key: ./skey.jwk

Documentation

Overview

Copyright 2022-2024 Contributors to the Veraison project. SPDX-License-Identifier: Apache-2.0