Configuration

Command-line arguments

The Corsha Primer uses the triple of a Machine ID, Build ID, and Job ID to identify a machine that will be deployed using the generated Authenticator Secret.

When running the primer as a native binary or from Docker, the arguments are:

./mstream-primer <Machine ID> <Build ID> <Job ID>

Argument	Description
Machine ID	A description of the workload that will be deployed with a Corsha Authenticator
Build ID	Describes the variant of the workload that will be deployed, for example a Git branch when deploying from CICD
Job ID	A unique identifier for each instance of this Machine and Build that will be deployed, such as a Kubernetes pod name or a Docker container name

info

These three arguments must be unique for each generated Authenticator Secret. When deploying new Authenticators for an existing workload, update the Build and/or Job ID. If the Authenticator secret is for a new workload, use a unique Machine ID that describes the workload.

For example when deploying 3 machines that perform the same workload, the Primer would be executed as:

./mstream-primer "myCloudWorkload" "myGitBranch" "1"
./mstream-primer "myCloudWorkload" "myGitBranch" "2"
./mstream-primer "myCloudWorkload" "myGitBranch" "3"

Flags

Flags	Description
--ca-cert	(Optional) The path to a bundle of PEM-encoded CA certs used to extend trust

Environment variables

Primer Secret

The Primer Secret is obtained in the Console

Variable Name	Description	Example
PRIMER_SECRET	A JSON Web Token (JWT) that authorizes a Primer to fetch Authenticator Secrets	JWT-formatted string

Primer Service Network Configuration

The Primer obtains Authenticator Secrets from the Primer Service that is running in the Corsha Control Plane. These values are provided in your Deployment Guide.

Variable Name	Description	Example
PRIMER_SERVICE_HOST	Hostname of the primer service	auth-server-example-primer.example.com
PRIMER_SERVICE_PORT	Network port number of the primer service	443