The Broker is capable of encrypting passwords and other security items stored in the Broker's configuration. This is means that items such as keystore/truststore passwords, JDBC passwords, and LDAP passwords can be stored in the configuration in a form that is difficult to read.
The Broker ships with an encryptor implementation called AESGCMKeyFile .
This uses a securely generated random key of 256bit
[9]
to encrypt the secrets stored within a key file. Of course, the key itself must be guarded carefully,
otherwise the passwords encrypted with it may be compromised. For this reason, the Broker ensures
that the file's permissions allow the file to be read exclusively by the user account used for running
the Broker.
Important
If the keyfile is lost or corrupted, the secrets will be irrecoverable.
The AESGCMKeyFile encryptor provider is
enabled/disabled via the Broker attributes
within the Web Management Console. On enabling the provider, any existing passwords within the
configuration will be automatically rewritten in the encrypted form.
If the AESGCMKeyFile encryptor implementation does not meet the needs of
the user, perhaps owing to the security standards of their institution, the
ConfigurationSecretEncrypter interface is designed as an extension point.
Users may implement their own implementation of ConfigurationSecretEncrypter perhaps to employ
stronger encryption or delegating the storage of the key to an Enterprise Password
Safe.
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners