TRUST

Easy Installation

Deployment Guide

Deploy the DAR and client application to your Canton node to start issuing domain verification credentials.

1.

Before you start

  • A running Canton participant node
  • Docker installed on your infrastructure
  • An OIDC-compliant IAM provider (e.g. Keycloak, Auth0) configured for your node
  • Access to your participant node’s JSON API URL

If your NaaS provider has already installed 7Trust on your node, skip to section 5.

ON THIS PAGE

  1. Before you start
  2. Deploy the DAR
  3. Deploy the client app
  4. Environment variables
  5. First login

2.

Deploy the DAR

Download the latest DAR file from the public C7 GitHub repository.

Download DAR file

Upload the DAR file to your Canton participant node using your node’s DAR upload interface.

3.

Deploy the client application

The client app is a Docker image running an Nginx web server. It connects to your OIDC IAM provider to authenticate users and to your participant node to authorise their actions. Pull the image from the C7 GHCR registry.

TestNet

docker pull ghcr.io/c7-digital/7trust-client:test

MainNet

docker pull ghcr.io/c7-digital/7trust-client:prod

Once pulled, deploy the image to your infrastructure. The server listens on port 8080 — set up ingress accordingly.

4.

Configure environment variables

The application is configured via environment variables. Set these before running the container.

VariableDescriptionRequired
CANTON_LEDGER_URLURL of your participant node’s JSON API. Used to create and exercise commands on contracts for the 
DomainOwnershipToken 
workflow.

http://participant-validator-c7-2.canton-c7-devnet.svc.cluster.local:7575		Required
OIDC_AUTHORITYURL of your OIDC-compliant authority provider. Must respond with JWT access tokens for users acting on your participant node.

https://keycloak.dev.global.canton.network.7trust.c7.digital/auth/realms/canton-c7-devnet		Required
OIDC_CLIENT_IDThe client ID of the OIDC provider handling user logins.

domain-verification		Required
AUTH0_AUTH_AUDIENCEAuth0-specific. Required only if using Auth0 as your IAM provider — Auth0 requires an audience attribute when requesting an access token.Optional

5.

First login

Once the site is running correctly you’ll see the login screen. Sign in via IAM/SSO or with a token and accept T&Cs.

Deployment guide

Download PDF