Hello,

>From what I understand from the documentation, the transit engine of
Hashicorp Vault is definitely supported for system properties. It is also
clear that the standard key/value engine of Hashicorp vault is supported
for sensitive processor properties (e.g. the password used to connect to an
MQTT broker in a ConsumeMQTT processor).

What I cannot tell is if NiFi supports using the transit engine for these
sensitive properties of processors.

I'd like to ensure that these properties are encrypted at rest inside of
the registry, but decrypted using the transit engine and a provided vault
encryption key at runtime.

Is this currently supported? Or is the only the standard key/value engine
supported for such properties?

Thanks,
Cannon

Reply via email to