Triunnia Labs

Control Panel

Setup and Administration for the Arch Platform

Configuration

Set Up Each Microservice Before Deployment

Screen

Description

Configure the name and type of the microservice, which determines which configuration screens are available.

Configure how the microservice is accessed, including its URLs, port, and client API key.

Configure how the microservice connects to and authenticates with the Application Api.

Configure the encryption settings used by the microservice's protected memory system.

Specify database connection strings for microservices that require Sql Server access.

Enable or disable optional features on the microservice, such as Hardware Security Module support.

Specify the connector URL for the YubiHSM 2 hardware security module when the HSM feature is enabled.

Configure the YubiHSM 2 parameters used by the Guardian when the HSM feature is enabled.

Specify the data path where the Files Api stores its files.

Configure Postmark integration by specifying the server token and webhook authentication credentials.

Deployment

Get Configuration Values and Bring Services Online

Screen

Description

Get encrypted configuration settings formatted for use in an appsettings.json file.

Get encrypted configuration settings formatted as environment variables for Docker deployments.

Unseal the Application Api via the Guardian, required after every restart when the HSM feature is enabled.

Diagnostics

Verify and Troubleshoot Running Services

Screen

Description

Verify that a microservice has started and is in a healthy state.

Compare the microservice's running configuration against what the Control Panel has specified.

Test microservice-to-Application Api authentication and client-to-microservice authentication in isolation.