This section will help us integration 2 popular databases with HashiCorp Vault, namely Oracle MySQL and Microsoft MSSQL.
Let's start with Oracle's MySQL
vagrant up --provision-with mysql
Bringing machine 'user.local.dev' up with 'virtualbox' provider...
==> user.local.dev: Checking if box 'ubuntu/xenial64' version '20190918.0.0' is up to date...
==> user.local.dev: [vagrant-hostsupdater] Checking for host entries
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 hashicorp.local.dev
==> user.local.dev: Running provisioner: mysql (shell)...
user.local.dev: Running: /var/folders/7j/gsrjvmds05n53ddg28krf4_80001p9/T/vagrant-shell20191114-11217-1i13id.sh
user.local.dev: mysql
user.local.dev: mysql
user.local.dev: WARNING! This will remove:
user.local.dev: - all stopped containers
user.local.dev: - all networks not used by at least one container
user.local.dev: - all volumes not used by at least one container
user.local.dev: - all dangling images
user.local.dev: - all dangling build cache
user.local.dev:
user.local.dev: Are you sure you want to continue? [y/N]
user.local.dev: Deleted Volumes:
user.local.dev: aa92e07b88059445d76f25571d5a7c819888abb261f20b81a156c97076624cc9
user.local.dev: Total reclaimed space: 171.2MB
user.local.dev: Reading package lists...
user.local.dev: Building dependency tree...
user.local.dev:
user.local.dev: Reading state information...
user.local.dev: mysql-client is already the newest version (5.7.27-0ubuntu0.16.04.1).
user.local.dev: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
user.local.dev: 6e63bb00598d3eb6e1a86a8ebf70575fe086339608c9b0274facc6e591a1e32b
user.local.dev: Instructions
user.local.dev: mysql -h 127.0.0.1 -u root -ppassword
Let's verify that our mysql container is up and accepting connections
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"show databases;\""
mysql: [Warning] Using a password on the command line interface can be insecure.
+--------------------+
| Database |
+--------------------+
| db |
| information_schema |
| mysql |
| performance_schema |
| sys |
+--------------------+
Now let's bring up Vault, lets make sure it's running, by doing:
vagrant up --provision-with vault
Bringing machine 'user.local.dev' up with 'virtualbox' provider...
==> user.local.dev: Checking if box 'ubuntu/xenial64' version '20190918.0.0' is up to date...
==> user.local.dev: [vagrant-hostsupdater] Checking for host entries
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 consul-user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 vault-user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 nomad-user.local.dev
==> user.local.dev: Running provisioner: vault (shell)...
user.local.dev: Running: /var/folders/7j/gsrjvmds05n53ddg28krf4_80001p9/T/vagrant-shell20191024-26402-1ms4n4s.sh
user.local.dev: Vault already installed and running
user.local.dev: Vault http:https://localhost:8200/ui and enter the following codes displayed below
user.local.dev: Unseal Key 1: aRBITqqWe57Tl38J9avHZVoow2oC6C2qjEgWFqQAV4Z1
user.local.dev: Unseal Key 2: +Z0RHNn1lBkKas5WIiuXYha5LTA/7i+ncLBdJafBpNs8
user.local.dev: Unseal Key 3: 0Wg9qT6rNeB1fm5CDUdEuM8nWtI6Jt5PTAT6z0HkZRBY
user.local.dev: Unseal Key 4: ysw0/LJPGy4jfhoPG6Lvm+ARBzkT8Q70cXgvPRZRd5Pi
user.local.dev: Unseal Key 5: g6el6P2RAtwymn8tHE38ltdyiOeEf1Wfn8+8kShxIdZP
user.local.dev:
user.local.dev: Initial Root Token: s.XmyUDCIJkHMA4QgeDO6oykz6
user.local.dev:
user.local.dev: Vault initialized with 5 key shares and a key threshold of 3. Please securely
user.local.dev: distribute the key shares printed above. When the Vault is re-sealed,
user.local.dev: restarted, or stopped, you must supply at least 3 of these keys to unseal it
user.local.dev: before it can start servicing requests.
user.local.dev:
user.local.dev: Vault does not store the generated master key. Without at least 3 key to
user.local.dev: reconstruct the master key, Vault will remain permanently sealed!
user.local.dev:
user.local.dev: It is possible to generate new unseal keys, provided you have a quorum of
user.local.dev: existing unseal keys shares. See "vault operator rekey" for more information.
Unseal the Vault and login with the root token.
Now let's enable the database secrets engine. Top right please click on Enable new Engine and select Database and click Next
Now let's create credentials for Vault in mysql, vault will basically be the only static user in mysql and will only have create rights for Users.
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"CREATE USER 'vault'@'%' IDENTIFIED BY 'password';\""
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"GRANT ALL PRIVILEGES ON *.* TO 'vault'@'%' WITH GRANT OPTION;\""
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"GRANT CREATE USER ON *.* to 'vault'@'%';\""
Now let's configure the vault user in Vaults database secrets engine to create users for our default database db
vagrant ssh -c "vault write database/config/db plugin_name=mysql-database-plugin connection_url='{{username}}:{{password}}@tcp(localhost:3306)/' allowed_roles='mysql-role' username='vault' password='password'"
You will see we used allowed_roles='mysql-role' that does not exist yet, let's create it now
vagrant ssh -c "vault write database/roles/mysql-role db_name=db creation_statements=\"CREATE USER '{{name}}'@'%' IDENTIFIED BY '{{password}}';GRANT ALL PRIVILEGES ON db.* TO '{{name}}'@'%';\" default_ttl='1h' max_ttl='24h'"
Success! Data written to: database/roles/mysql-role
Let's quickly check the users before we ask Vault to give us credentials
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"SELECT User, Host from mysql.user;\""
mysql: [Warning] Using a password on the command line interface can be insecure.
+------------------+-----------+
| User | Host |
+------------------+-----------+
| root | % |
| vault | % |
| mysql.infoschema | localhost |
| mysql.session | localhost |
| mysql.sys | localhost |
| root | localhost |
+------------------+-----------+
Now let's ask Vault for credentials
vagrant ssh -c "vault read database/creds/mysql-role"
Key Value
--- -----
lease_id database/creds/mysql-role/IhHPq0RcdmDdTIjsfLBePLcp
lease_duration 1h
lease_renewable true
password A1a-0bdhOg0OiZQV0TTP
username v-root-mysqlrole-zV7t3V0bJFZZJTg
Ok now let's check the user table again for the new users existence based on the role mysql-role
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"SELECT User, Host from mysql.user;\""
mysql: [Warning] Using a password on the command line interface can be insecure.
+-----------------------------------+-----------+
| User | Host |
+-----------------------------------+-----------+
| root | % |
| v-root-mysql-role-zV7t3V0bJFZZJTg | % |
| vault | % |
| mysql.infoschema | localhost |
| mysql.session | localhost |
| mysql.sys | localhost |
| root | localhost |
+-----------------------------------+-----------+
Let's ask Vault for the connection details to mysql
vagrant ssh -c "curl --header 'X-Vault-Token:s.h7kojucmDDULDmxHAyr7jhrE' http:https://localhost:8200/v1/database/creds/mysql-role"
{
"request_id":"23116091-f72b-80f9-fb0e-6ce5418bae1d",
"lease_id":"database/creds/mysql-role/7wMxCUzNcEaOrvCspBhXnjTM",
"renewable":true,
"lease_duration":3600,
"data":{
"password":"A1a-XhNU8s4P0Ph5Se9O",
"username":"v-root-mysql-role-kmFADTyAAfv7LS0"
},
"wrap_info":null,
"warnings":null,
"auth":null
}
a simple way to use this is passing credentials to a docker container, like so:
response=$(curl --header "X-Vault-Token:s.h7kojucmDDULDmxHAyr7jhrE" http:https://localhost:8200/v1/database/creds/mysql-role)
export DBPASSWORD=$(echo $response | jq -r .data.password)
export DBUSERNAME=$(echo $response | jq -r .data.username)
docker run --name webapp -d -p 8080:80 --rm -e DATABASE_URL=mysql+pymysql:https://DBUSERNAME:[email protected]/db webapp:latest
If we check the credentials after an hour, you will see that they have been removed by Vault
vagrant ssh -c "mysql -h 127.0.0.1 -u root -ppassword -e \"SELECT User, Host from mysql.user;\""
mysql: [Warning] Using a password on the command line interface can be insecure.
+------------------+-----------+
| User | Host |
+------------------+-----------+
| root | % |
| vault | % |
| mysql.infoschema | localhost |
| mysql.session | localhost |
| mysql.sys | localhost |
| root | localhost |
+------------------+-----------+
vagrant up --provision-with mssql
Bringing machine 'user.local.dev' up with 'virtualbox' provider...
==> user.local.dev: Checking if box 'ubuntu/xenial64' version '20190918.0.0' is up to date...
==> user.local.dev: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> user.local.dev: available! You currently have version '20190918.0.0'. The latest is version
==> user.local.dev: '20191114.0.0'. Run `vagrant box update` to update.
==> user.local.dev: [vagrant-hostsupdater] Checking for host entries
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 user.local.dev
==> user.local.dev: [vagrant-hostsupdater] found entry for: 10.9.99.10 hashicorp.local.dev
==> user.local.dev: Running provisioner: mssql (shell)...
user.local.dev: Running: /var/folders/7j/gsrjvmds05n53ddg28krf4_80001p9/T/vagrant-shell20191120-4643-g6u6tj.sh
user.local.dev: mssql
user.local.dev: mssql
user.local.dev: 3ae09d27c879acb4a8c328f42805754070584a96b188dc3277b4b3653c232df8
user.local.dev: Instructions
user.local.dev: vagrant ssh
user.local.dev: docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "CREATE DATABASE mssql"
user.local.dev: docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "SELECT name, database_id, create_date FROM sys.databases"
user.local.dev: vault secrets enable database
user.local.dev: vault write database/config/mssql \
user.local.dev: plugin_name=mssql-database-plugin \
user.local.dev: connection_url='sqlserver:https://{{username}}:{{password}}@localhost:1433' \
user.local.dev: allowed_roles="mssql" \
user.local.dev: username="sa" \
user.local.dev: password="P@ssw0rd"
user.local.dev: vault write database/roles/mssql \
user.local.dev: db_name=mssql \
user.local.dev: creation_statements="CREATE LOGIN [{{name}}] WITH PASSWORD = '{{password}}'; \
user.local.dev: CREATE USER [{{name}}] FOR LOGIN [{{name}}]; \
user.local.dev: GRANT SELECT ON SCHEMA::dbo TO [{{name}}];" \
user.local.dev: default_ttl="1h" \
user.local.dev: max_ttl="24h"
user.local.dev: vault read database/creds/mssql
user.local.dev: docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "SELECT * FROM sysusers"
Now that MSSQL is launched let's get started.
We SSH into Vagrant vagrant ssh
Now let's create a database called mssql
docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "CREATE DATABASE mssql"
Now let's verify that the database was successfully created.
docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "SELECT name, database_id, create_date FROM sys.databases"
name database_id create_date
-------------------------------------------------------------------------------------------------------------------------------- ----------- -----------------------
master 1 2003-04-08 09:13:36.390
tempdb 2 2019-11-20 03:23:54.157
model 3 2003-04-08 09:13:36.390
msdb 4 2018-06-13 18:27:29.220
mssql 5 2019-11-20 03:24:03.043
(5 rows affected)
Let's ensure the database engine in vault secrets enable database
Success! Enabled the database secrets engine at: database/
Now let's enable the database in Vault.
vault write database/config/mssql \ plugin_name=mssql-database-plugin \ connection_url='sqlserver:https://{{username}}:{{password}}@localhost:1433' \ allowed_roles="mssql" \ username="sa" \ password="P@ssw0rd"
And create a role that are allowed to fetch credentials from Vault.
vault write database/roles/mssql \ db_name=mssql \ creation_statements="CREATE LOGIN [{{name}}] WITH PASSWORD = '{{password}}'; \ CREATE USER [{{name}}] FOR LOGIN [{{name}}]; \ GRANT SELECT ON SCHEMA::dbo TO [{{name}}];" \ default_ttl="1h" \ max_ttl="24h"
Now let's ask Vault to create some credentials for us
vault read database/creds/mssql
And let's see if the credentials were created
docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U v-root-mssql-5nBk5IA9hydRgzOkgB8M-1574220338 -P A1a-dninssZ6v3mNBOfK -Q "SELECT * FROM sys.server_principals"
name principal_id sid type type_desc is_disabled create_date modify_date default_database_name default_language_name credential_id owning_principal_id is_fixed_role
-------------------------------------------------------------------------------------------------------------------------------- ------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---- ------------------------------------------------------------ ----------- ----------------------- ----------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- ------------------- -------------
sa 1 0x01 S SQL_LOGIN 0 2003-04-08 09:10:35.460 2019-11-20 03:23:54.283 master us_english NULL NULL 0
public 2 0x02 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 0
sysadmin 3 0x03 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
securityadmin 4 0x04 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
serveradmin 5 0x05 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
setupadmin 6 0x06 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
processadmin 7 0x07 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
diskadmin 8 0x08 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
dbcreator 9 0x09 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
bulkadmin 10 0x0A R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
v-root-mssql-5nBk5IA9hydRgzOkgB8M-1574220338 262 0x893ADA262238054280B2F0FE8F634F68 S SQL_LOGIN 0 2019-11-20 03:25:38.777 2019-11-20 03:25:38.790 master us_english NULL NULL 0
(11 rows affected)
Now let's wait an hour and check if Vault has removed the credential
docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U v-root-mssql-5nBk5IA9hydRgzOkgB8M-1574220338 -P A1a-dninssZ6v3mNBOfK -Q "SELECT * FROM sys.server_principals"
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login failed for user 'v-root-mssql-5nBk5IA9hydRgzOkgB8M-1574220338'..
vagrant@riaannolan:~$ docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P P@ssw0rd -Q "SELECT * FROM sys.server_principals"`
name principal_id sid type type_desc is_disabled create_date modify_date default_database_name default_language_name credential_id owning_principal_id is_fixed_role
-------------------------------------------------------------------------------------------------------------------------------- ------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---- ------------------------------------------------------------ ----------- ----------------------- ----------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- ------------------- -------------
sa 1 0x01 S SQL_LOGIN 0 2003-04-08 09:10:35.460 2019-11-20 03:32:15.807 master us_english NULL NULL 0
public 2 0x02 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 0
sysadmin 3 0x03 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
securityadmin 4 0x04 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
serveradmin 5 0x05 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
setupadmin 6 0x06 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
processadmin 7 0x07 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
diskadmin 8 0x08 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
dbcreator 9 0x09 R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
bulkadmin 10 0x0A R SERVER_ROLE 0 2009-04-13 12:59:06.030 2009-04-13 12:59:06.030 NULL NULL NULL 1 1
##MS_SQLResourceSigningCertificate## 101 0x0106000000000009010000005488E76D0CC357B76B75580222F2B12E78E2E0A2 C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:10.900 2018-06-13 18:27:10.900 master NULL NULL NULL 0
##MS_SQLReplicationSigningCertificate## 102 0x010600000000000901000000797A1CDCF4B554BB72461A573EBF37DF38A8E95A C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:10.900 2018-06-13 18:27:10.900 master NULL NULL NULL 0
##MS_SQLAuthenticatorCertificate## 103 0x010600000000000901000000933CACCAA1A0D21D750FC6ECF27EC0B67452CBD6 C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:10.903 2018-06-13 18:27:10.903 master NULL NULL NULL 0
##MS_PolicySigningCertificate## 105 0x0106000000000009010000002B99E5CBD00E8F5971F851F7E2C791D55223EE70 C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:10.903 2018-06-13 18:27:10.903 master NULL NULL NULL 0
##MS_SmoExtendedSigningCertificate## 106 0x010600000000000901000000BD7C7E85333757CFDF554A95CC657D7FCDBD57B0 C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:10.903 2018-06-13 18:27:10.903 master NULL NULL NULL 0
##MS_PolicyEventProcessingLogin## 256 0x444C3BC8EC6FCB43BF018A3118A7E2AE S SQL_LOGIN 1 2018-06-13 18:27:36.807 2019-11-20 03:32:14.483 master us_english NULL NULL 0
##MS_PolicyTsqlExecutionLogin## 257 0x64EDBF6D55705C48BAD91D921E8340BB S SQL_LOGIN 1 2018-06-13 18:27:36.810 2019-11-20 03:32:14.483 master us_english NULL NULL 0
##MS_AgentSigningCertificate## 258 0x0106000000000009010000005689043243A5B65B41804742FB020E1692F1FD59 C CERTIFICATE_MAPPED_LOGIN 0 2018-06-13 18:27:41.753 2018-06-13 18:27:41.760 master us_english NULL NULL 0
BUILTIN\Administrators 259 0x01020000000000052000000020020000 G WINDOWS_GROUP 0 2018-06-13 18:29:22.210 2018-06-13 18:29:22.220 master us_english NULL NULL 0
NT AUTHORITY\NETWORK SERVICE 260 0x010100000000000514000000 U WINDOWS_LOGIN 0 2019-11-20 03:32:15.817 2019-11-20 03:32:18.840 master us_english NULL NULL 0
NT AUTHORITY\SYSTEM 261 0x010100000000000512000000 U WINDOWS_LOGIN 0 2019-11-20 03:32:15.823 2019-11-20 03:32:15.830 master us_english NULL NULL 0
(21 rows affected)
vagrant up --provision-with postgresql
Bringing machine 'hashiqube0.service.consul' up with 'virtualbox' provider...
==> hashiqube0.service.consul: Checking if box 'ubuntu/bionic64' version '20200429.0.0' is up to date...
==> hashiqube0.service.consul: [vagrant-hostsupdater] Checking for host entries
==> hashiqube0.service.consul: [vagrant-hostsupdater] found entry for: 10.9.99.10 hashiqube0.service.consul
==> hashiqube0.service.consul: [vagrant-hostsupdater] found entry for: 10.9.99.10 hashiqube0.service.consul
==> hashiqube0.service.consul: Running provisioner: postgresql (shell)...
hashiqube0.service.consul: Running: /var/folders/7j/gsrjvmds05n53ddg28krf4_80001p9/T/vagrant-shell20200831-13614-16pi9p8.sh
hashiqube0.service.consul: postgres
hashiqube0.service.consul: postgres
hashiqube0.service.consul: Download complete
hashiqube0.service.consul: 38fa0d496534: Verifying Checksum
hashiqube0.service.consul: 38fa0d496534: Download complete
hashiqube0.service.consul: bf5952930446: Pull complete
hashiqube0.service.consul: 26dc6fdd7b2d: Verifying Checksum
hashiqube0.service.consul: 26dc6fdd7b2d: Download complete
hashiqube0.service.consul: 9577476abb00: Pull complete
hashiqube0.service.consul: 2bd105512d5c: Pull complete
hashiqube0.service.consul: b1cd21c26e81: Pull complete
hashiqube0.service.consul: 3c5032512cf3: Verifying Checksum
hashiqube0.service.consul: 3c5032512cf3: Download complete
hashiqube0.service.consul: 34a7c86cf8fc: Pull complete
hashiqube0.service.consul: 274e7b0c38d5: Pull complete
hashiqube0.service.consul: 3e831b350d37: Pull complete
hashiqube0.service.consul: 38fa0d496534: Pull complete
hashiqube0.service.consul: 26910ececf99: Verifying Checksum
hashiqube0.service.consul: 26910ececf99: Download complete
hashiqube0.service.consul: 0339413523e8: Verifying Checksum
hashiqube0.service.consul: 0339413523e8: Download complete
hashiqube0.service.consul: d61df7db53da: Verifying Checksum
hashiqube0.service.consul: d61df7db53da: Download complete
hashiqube0.service.consul: c989da35e5c0: Verifying Checksum
hashiqube0.service.consul: c989da35e5c0: Download complete
hashiqube0.service.consul: c989da35e5c0: Pull complete
hashiqube0.service.consul: 26dc6fdd7b2d: Pull complete
hashiqube0.service.consul: 3c5032512cf3: Pull complete
hashiqube0.service.consul: 26910ececf99: Pull complete
hashiqube0.service.consul: 0339413523e8: Pull complete
hashiqube0.service.consul: d61df7db53da: Pull complete
hashiqube0.service.consul: Digest: sha256:9f325740426d14a92f71013796d98a50fe385da64a7c5b6b753d0705add05a21
hashiqube0.service.consul: Status: Downloaded newer image for postgres:latest
hashiqube0.service.consul: 3213b29cefa1c04b46c220b2da42c761aeb73e05c70da3174965646c75a96cfd
hashiqube0.service.consul: ++++ Vault already installed and running
hashiqube0.service.consul: ++++ Vault http:https://localhost:8200/ui and enter the following codes displayed below
hashiqube0.service.consul: ++++ Auto unseal vault
hashiqube0.service.consul: ++++ Show users in database
hashiqube0.service.consul: List of roles
hashiqube0.service.consul: Role name | Attributes | Member of
hashiqube0.service.consul: -----------+------------------------------------------------------------+-----------
hashiqube0.service.consul: root | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
hashiqube0.service.consul: ++++ Enable Vault Database PostgreSQL secret engine
hashiqube0.service.consul: ++++ Configure PostgreSQL
hashiqube0.service.consul: rnings were returned from Vault:
hashiqube0.service.consul:
hashiqube0.service.consul: * Password found in connection_url, use a templated url to enable root
hashiqube0.service.consul: rotation and prevent read access to p
hashiqube0.service.consul: a
hashiqube0.service.consul: s
hashiqube0.service.consul: s
hashiqube0.service.consul: w
hashiqube0.service.consul: ord information.
hashiqube0.service.consul: ++++ Create a role
hashiqube0.service.consul: Success! Data written to: database/roles/postgresql-role
hashiqube0.service.consul: ++++ Create policy
hashiqube0.service.consul: Success! Uploaded policy: apps
hashiqube0.service.consul: ++++ Create new token
hashiqube0.service.consul: ++++ New Token: s.oUPWzOf9xJw1fLQiHaFGOdFe
hashiqube0.service.consul: ++++ Create new connection with token
hashiqube0.service.consul: Key Value
hashiqube0.service.consul: --- -----
hashiqube0.service.consul: lease_id database/creds/postgresql-role/WFLWSDwEwDSgou9qmJrBpk9m
hashiqube0.service.consul: lease_duration 1h
hashiqube0.service.consul: lease_renewable true
hashiqube0.service.consul: password A1a-WgK3eOqo10hHFXpa
hashiqube0.service.consul: username v-token-postgres-3AhBH3pbmVNnkbxXV8K3-1598841098
hashiqube0.service.consul: ++++ Now show users in database again with new user created
hashiqube0.service.consul: List of roles
hashiqube0.service.consul: Role name | Attributes | Member of
hashiqube0.service.consul: --------------------------------------------------+------------------------------------------------------------+-----------
hashiqube0.service.consul: root | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
hashiqube0.service.consul: v-token-postgres-3AhBH3pbmVNnkbxXV8K3-1598841098 | Password valid until 2020-08-31 03:31:43+00 | {}
```