Conjur Intro

Tools and scripts utilities that make it easier to make, manage, and run demos

Demos

• AWS Cluster
• Conjur Cluster
• Certificate Authority

Tools

• Generate Signed Certificates
• K6 Performance Tests

CLI Tools

This project includes a CLI which simplifies the process of running a variety of scenarios.

Workflow Examples

Deploy a master auto-failover cluster (behind L4 load balancer).

$ bin/dap --provision-master
$ bin/dap --provision-standbys
$ bin/dap --enable-auto-failover

Given the above, to add a follower (behind L7 load balancer), add data, and validate retrieval:

$ bin/dap --provision-follower
$ bin/api --load-sample-policy-and-values
$ bin/api --fetch-secrets

Next, let's trigger an auto-failover event:

$ bin/dap --trigger-failover

Upgrade and rebuild cluster:

$ bin/dap --upgrade-master <version>
$ bin/dap --provision-standbys --version <version>
$ bin/dap --enable-auto-failover
$ bin/dap --provision-follower --version <version>

and finally, validate:

$ bin/api --fetch-secrets

Follower could be also deployed using Kind into Kubernetes cluster:

$ bin/dap --provision-k8s-follower

More information about way of how the Follower is deployed into Kubernetes cluster can be found in README.md

Working with Podman

The project is enabled to work with Podman instead of Docker. To use Podman the above commands can be replaced as follows:

$ bin/podman-dap --provision-master
$ bin/podman-dap --provision-standbys
$ bin/podman-dap --enable-auto-failover

Similarly bin/api and bin/cli can be replaced with bin/podman-api and bin/podman-cli.

To connect to the UI in the browser, use ports 10443(through HA proxy) or 10444(Conjur)

---

bin/dap

bin/dap provides a dead simple mechanism for starting DAP in a variety of configurations and workflows. It provides visibility into the commands required to perform various workflows.

Flags

Flag	Type	Outcome	Notes
--create-backup	action	• Creates a backup	Requires configured master
--dry-run	configuration	Only print configuration commands
--enable-auto-failover	action	• Configures Master cluster with auto-failover	Requires configured master and standbys
--generate-dh	configuration	• Disables the mounting of pre-generated DH params inside the master so they're generated on the fly
--help		Shows all available arguments
--import-custom-certificates	action	• Imports pre-generated 3rd-party certificates	Requires configured master
--promote-standby	action	• Stops the current master • Promotes a standby	Requires configured standbys and no auto-failover
--provision-follower	action	• Removes follower if present • Starts a DAP container and a Layer 7 load balancer • Generates a follower seed • Configures follower	Requires configured master
--provision-k8s-follower	action	• Removes follower if present • Configures follower inside kubernetes cluster ran by kind	Requires configured master
--provision-master	action	• Starts a DAP container and Layer 4 load balancer • Configures with account demo and password MySecretP@ss1
--provision-standbys	action	• Removes standbys if present • Starts two DAP containers • Generates standby seed files • Configures standbys • Enable Synchronous Standby	Requires configured master
--restore-from-backup	action	• Removes auto-failover (if enabled) • Stops and renames master • Starts new DAP container • Restores master from backup	Requires a previously created backup
--stop	action	Stops and removes all containers
--trigger-failover	action	• Stops current master	Requires an auto-failover cluster
--trust-follower-proxy	action	• Adds Follower load balancer as a trusted proxy	Requires configured follower
--upgrade-master <version>	action	• Removes auto-failover (if enabled) • Generates a backup • Stops and removes master • Starts new DAP container • Restores master from backup	Requires configured master
--version <version>	configuration	Version of DAP to use (defaults to latest)
--k8s-follower-version <version>	configuration	Version of K8S-Follower to use (defaults to latest)
--follower-to-master-connection <on/off>	action	Pauses or unpauses follower connection to master	Requires a configured master

bin/api

bin/api enables some common policy and API flows.

Flags

Flag	Type	Outcome	Notes
--against-master	configuration	Runs read actions against the master
--authenticate-user	action	• Authenticates with default user and password • Displays the resulting authentication token
--fetch-secrets	action	• Authenticates • Retrieves variable values	Run against follower unless --against-master flag is present
--load-policy	action	• Authenticates • Loads policy	Run against master
--load-policy-and-values	action	• Authenticates • Loads policy and variable values	Run against master, equivalent to running '--load-policy' and '--set-secrets'
--password <password>	configuration	Uses a non-default password for authentication
--set-secrets	action	• Authenticates • Sets variable values	Requires --load-policy before running
--user <conjur-user>	configuration	Uses a non-default (admin) user for authentication

Start a single DAP instance

To start a single DAP instance:

$ bin/dap --provision-master

This instance runs behind an HAProxy load balancer and is available at: [https://localhost]. Login:

• Account demo
• User: admin
• Password: MySecretP@ss1

Start a DAP Cluster with Follower

To start a basic HA DAP cluster (self-signed certificates, no Master Key encryption) and a Follower:

$ bin/dap --provision-master
$ bin/dap --provision-standbys
$ bin/dap --provision-follower

This instance runs behind an HAProxy load balancer and is available at: [https://localhost]. Login:

• Account demo
• User: admin
• Password: MySecretP@ss1

Available Flags

The following flags are available:

Usage: bin/dap single [options]

    --create-backup                   Creates a backup|Requires configured master
    --dry-run                         Print configuration commands with executing
    --enable-auto-failover            Configures Master cluster with auto-failover (Requires configured master and standbys)
    --h, --help                       Shows this help message
    --import-custom-certificates      Imports pre-generated 3rd-party certificates (Requires configured master)
    --promote-standby                 Stops the current master and promotes a standby (Requires configured standbys and no auto-failover)
    --provision-follower              Configures follower behind a Layer 7 load balancer (Requires configured master)
    --provision-k8s-follower          Configures follower inside kubernetes cluster ran by kind (Requires configured master)
    --provision-master                Configures a DAP Master with account `demo` and password `MySecretP@ss1` behind a Layer 4 load balancer
    --provision-standbys              Deploys and configures two standbys (Requires configured master)
    --restore-from-backup             Restores a master from backup|Requires a previously created backup
    --stop                            Stops all containers and cleans up cached files
    --trigger-failover                Stops current master (Requires an auto-failover cluster)
    --trust-follower-proxy            Adds Follower load balancer as a trusted proxy (Requires a configured follower)
    --upgrade-master <version>        Restores master from backup (Requires configured master)
    --version <version>               Version of DAP to use (defaults to latest build)
    --k8s-follower-version <version>  Version of K8S-Follower to use (defaults to latest build)

bin/cli

bin/cli is a proxy script, sending all subsequent arguments to a Conjur CLI container. This provides a simple mechanism for loading policy and interacting with Conjur.

Loading policy

The policy folder contains sample policy which can be loaded with:

$ bin/cli conjur policy replace -b root -f policy/users.yml
$ bin/cli conjur policy load -b root -f policy/policy.yml
$ bin/cli conjur policy load -b staging -f policy/apps/myapp.yml
$ bin/cli conjur policy load -b production -f policy/apps/myapp.yml
$ bin/cli conjur policy load -b root -f policy/application_grants.yml
$ bin/cli conjur policy load -b root -f policy/hosts.yml

Setting/Retrieving a Variable

bin/cli conjur variable set -i production/myapp/database/username -v my-username
bin/cli conjur variable set -i production/myapp/database/password -v my-password
bin/cli conjur variable set -i production/myapp/database/url -v https://my-database.mycompany.com
bin/cli conjur variable set -i production/myapp/database/port -v 5432

Validating Packages

This project can also be used to verify PRs, by installing the branch specific package (created by Jenkins). To begin, download the .deb package. After starting Conjur, packages can be installed with:

# Start Conjur
$ bin/dap --provision-master --version 5.11.0

Next in a new tab:

$ bin/install ~/Downloads/conjur-ui_2.10.9.1-e389f20_amd64.deb

The install script will install the package into the running Conjur appliance and restart the Conjur service.

You can view the contents of this package by running:

$ docker compose exec conjur-master-1.mycompany.local ls -a /opt/conjur/possum/

Performance Tests

Conjur Intro includes support for running a simple load test against a running instance.

# Start Conjur
$ bin/dap --provision-master
$ bin/dap --provision-follower

# Locally run metrics server (statsd with graphite visualization)
$ ./tools/performance-tests/k6/bin/metrics --start

# Optionally, load policies and 150k secrets (this might take around an hour)
$ ./bin/load-benchmark-data --accounts_per_safe 200 --safes 15 --hosts 300 --users 150 --all-properties-synchronized

# To integrate with statsD, set ENABLE_STATSD to true:
$ ENABLE_STATSD=true ./bin/load-benchmark-data --accounts_per_safe 200 --safes 15 --hosts 300 --users 150 --all-properties-synchronized

# Run load test without StatsD (default)
$ TEST_FILE=tools/performance-tests/k6/scenarios/read-individually.js ./bin/load-test

# Or run load test with StatsD enabled
$ ENABLE_STATSD=true TEST_FILE=tools/performance-tests/k6/scenarios/read-individually.js ./bin/load-test

The above test generates a report in the folder:

tmp/{TIMESTAMP}-test-name

Load is applied using k6. The k6 files are located at:

tools/performance-tests/k6

Scenarios for load testing are located at:

tools/performance-tests/k6/scenarios

Currently supported scenarios are:

• tools/performance-tests/k6/scenarios/read-individually.js - Read one secret at a time from Conjur by 12 VUs

• tools/performance-tests/k6/scenarios/read-batch-2-secrets.js - Read two secrets at a time from Conjur by 12 VUs

• tools/performance-tests/k6/scenarios/read-batch-4-secrets.js - Read four secrets at a time from Conjur by 12 VUs

• tools/performance-tests/k6/scenarios/create-policy.js - Create unique policies in Conjur by 1 VU in 500 iterations.

• tools/performance-tests/k6/scenarios/write-secrets.js - Write secrets to Conjur by 20 VUs.
  

  • Secrets are located at tools/performance-tests/k6/data/test-variable-secrets.csv
    
  • Number of VUs can be configured by setting K6_CUSTOM_VUS environment variable.

• tools/performance-tests/k6/scenarios/policy-number-test.js - Load simple policies into Conjur by 5 VUs.
  

  • Duration of the test can be configured by setting K6_CUSTOM_DURATION environment variable.

• tools/performance-tests/k6/scenarios/policy-depth-test.js - Keep loading nested policies until max depth is reached

• tools/performance-tests/k6/scenarios/list-and-batch-read.js - List all secrets in Conjur and then read a portion of them.

  • The purpose of this is to imitate how External Secrets Operator works when using the Find by Name or Find by Tag features. See <external-secrets/external-secrets#3364.

Contributing

We welcome contributions of all kinds to this repository. For instructions on how to get started and descriptions of our development workflows, please see our contributing guide.

License

This repository is licensed under Apache License 2.0 - see LICENSE for more details.