initial-config

This section lists the Corda CLI initial-config arguments. You can use these commands to manually perform various setup actions, as described in the Manual Bootstrapping section.

create-user-config

The create-user-config command creates the SQL script to add the RBAC Role-based access control. Also known as role-based security. A permission system to restrict system access based on assigned permissions. configuration for an initial admin user.

corda-cli.sh initial-config create-user-config -u <INITIAL-ADMIN-USERNAME> -p <INITIAL-ADMIN-PASSWORD> -l /tmp/db

corda-cli.cmd initial-config create-user-config -u <INITIAL-ADMIN-USERNAME> -p <INITIAL-ADMIN-PASSWORD> -l /tmp/db

create-db-config

The create-db-config command creates the SQL statements to insert the connection manager configuration for the database.

Argument	Description
-a, --is-admin	Specifies if this is an admin (DDL) connection. The default value is false.
-d, --description	Detailed information about the database connection.
-e, --passphrase	The passphrase for the default secrets service. This must match the value specified in the Corda deployment configuration for the database worker A worker that connects to, manages, and operates upon the database(s) used by the Corda cluster. This includes the cluster-level database schemas needed to store configuration data for the cluster, but also the separate databases/schemas used by each virtual node. .
--idle-timeout	The maximum time (in seconds) that a connection can stay idle in the pool. The default value is 120.
-j, --jdbc-url	The JDBC URL for the connection. This value is required.
--jdbc-pool-max-size	The maximum size of the JDBC connection pool. The default value is 10.
--jdbc-pool-min-size	The minimum size of the JDBC connection pool.
-k, --key	The vault key for the HashiCorp Vault external secrets service.
--keepalive-time	The interval time (in seconds) in which connections are tested for aliveness. The default value is 0.
-l, --location	The path to write the generated SQL files to.
--max-lifetime	The maximum time (in seconds) a connection can stay in the pool. The default value is 1800.
-n, --name	The name of the database connection. This value is required.
-p, --password	The password for the database connection. This value is required.
-s, --salt	The salt for the default secrets service. This must match the value specified in the Corda deployment configuration for the database worker.
-t, --type	Specifies the lookup service used to resolve secrets. This can be one of the following: CORDA — the default secrets service. The passphrase and salt values are used to decrypt values. VAULT — the HashiCorp Vault external secrets service. The vault-path and key values are used to resolve values.
-u, --user	The user name for the database connection. This value is required.
-v, --vault-path	The path to Corda created secrets for the HashiCorp Vault external secrets service.
--validation-timeout	The maximum time (in seconds) that the pool waits for a connection to be validated as alive. The default value is 5.

corda-cli.sh initial-config create-db-config -u <RBAC-USERNAME> -p <RBAC-PASSWORD> \
  --name corda-rbac --jbdc-url jdbc:postgresql://<DB-HOST>:<DB-PORT>/<DB=NAME> \
  --jdbc-pool-max-size <POOL-SIZE> --salt <SALT> --passphrase <PASSPHRASE> -l /tmp/db

corda-cli.cmd initial-config create-db-config -u <RBAC-USERNAME> -p <RBAC-PASSWORD> `
  --name corda-rbac --jbdc-url jdbc:postgresql://<DB-HOST>:<DB-PORT>/<DB=NAME> `
  --jdbc-pool-max-size <POOL-SIZE> --salt <SALT> --passphrase <PASSPHRASE> -l /tmp/db

create-crypto-config

The create-crypto-config command creates the SQL statements to insert the initial crypto configuration for the database. This operation must be performed after the cluster database is initialized but before the cluster is started.

corda-cli.sh initial-config create-crypto-config --salt <SALT> --passphrase <PASSPHRASE> -l /tmp/db

corda-cli.cmd initial-config create-crypto-config --salt <SALT> --passphrase <PASSPHRASE> -l /tmp/db