charm-vault/unit_tests
James Page 3b0e793feb Use secret_id's with vault-kv relation
In order to tighten the security around access to secrets stored
in a Vault KV secrets backend, generate a secret_id for each
accessing unit, using a response wrapping token which is passed
over the relation to the consuming application.

The consuming application will then use this token out-of-band of
Juju to retrieve the secret_id associated with the AppRole ID
directly from Vault.

Add a new action 'refresh-secrets' to force a renewal of secret_id's
and associated one-shot retrieval tokens across a deployment.

A token is only issued when a new approle is created or when
a refresh is initiated via the 'refresh-secrets' action.

Change-Id: I2cd173514377d65542ea4fa67ccf700ea4b6ab89
2018-05-08 12:46:01 +02:00
..
__init__.py Add snap channel support 2018-04-19 11:55:25 +01:00
test_lib_charm_vault.py Use secret_id's with vault-kv relation 2018-05-08 12:46:01 +02:00
test_reactive_vault_handlers.py Use secret_id's with vault-kv relation 2018-05-08 12:46:01 +02:00
test_utils.py Add action to allow charm to make calls to vault 2018-04-20 15:50:09 +00:00