This script configures a high availability DAP cluster with a master, follower and standby(s). The master cluster is load balanced for auto-failover.
Optionally, clusters can be configured with any or all of the following:
- Sample data
- Master Key encryption
- Custom third party certificates
- Disaster Recovery
- Particular Conjur version
To run this demo, you'll need the following installed:
- Docker
- Docker Composes
- Access to the Conjur Docker repository (or the Conjur Appliance Image locally)
- Bash
To view all options available, run the following:
$ bin/start --help
Provisions a Conjur cluster locally, using Docker.
Usage: start [options]
--auto-failover Configures the cluster for auto-failover
--custom-certs Installs custom certificates from the "files/certs" folder
--disaster-recovery Configures the cluster with a single Disaster Recovery node (only if the cluster is Auto-Failover)
-h, --help Shows this help message.
--load-data Loads sample policy along once th cluster
--master-key Encrypts certificates using a master key
--tag <conjur-tag> Starts a cluster with a particular appliance (defaults to 5.0-stable)
To stand up a simple cluster, without Master Key encryption, custom certificates, or sample data, run:
$ bin/start
To configure an Auto-Failover cluster, run:
$ bin/start --auto-failover
To configure a cluster with encrypted certificates using a master key:
$ bin/start --master-key
To configure a cluster using custom certificates:
$ bin/start --custom-certs
To load a configured cluster with sample data:
$ bin/start --load-data
To run a particular version of Conjur, pass the image tag in with the --tag
flag:
$ bin/start --tag 5.2.2-20181029194559-7305fae
Flags can be combined to provide combinations of these actions. Below is an example of how to configure a cluster with custom certificates, encrypted with a master key, and load sample data into the cluster:
$ bin/start --master-key --custom-certs --load-data
Navigate to localhost and login with the username: admin
and the password: MySecretP@ss1
.
To shutdown and cleanup your cluster after your done working, run:
$ bin/stop