diff options
| author | Keith Wall <kwall@apache.org> | 2014-10-12 15:48:18 +0000 |
|---|---|---|
| committer | Keith Wall <kwall@apache.org> | 2014-10-12 15:48:18 +0000 |
| commit | 39b5bc8a8456235540730c88922f60855a16e46b (patch) | |
| tree | ed495f958ebe78b2559dbbbb0c4e292e1555250f /qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml | |
| parent | 71c395d26e425571573b0bda06e23e5f84c1ca2c (diff) | |
| download | qpid-python-39b5bc8a8456235540730c88922f60855a16e46b.tar.gz | |
QPID-6108: [Java Broker Documentation] Rewrite HA documentation to reflect the new model and the include multi-node support.
* Correct many spelling errors
* Improve web-console documentation around add/edit/delete entities, and the setting of context variables
* Extract new top level section for backup/recovery
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1631195 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml')
| -rw-r--r-- | qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml b/qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml index 9fe2a4683e..2924f2859c 100644 --- a/qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml +++ b/qpid/doc/book/src/java-broker/Java-Broker-Security-Configuration-Encryption.xml @@ -23,7 +23,7 @@ <section id="Java-Broker-Security-Configuration-Encryption"> <title>Configuration Encryption</title> - <para> The Broker is capable of encypting passwords and other security items stored in the + <para> 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 configure in a form that is difficult to read.</para> @@ -69,6 +69,6 @@ the user, perhaps owing to the security standards of their institution, the <literal>ConfigurationSecretEncrypter</literal> interface is designed as an extension point. Users may implement their own implementation of ConfigurationSecretEncrypter perhaps to employ - stonger encryption or delegating the storage of the key to an Enterprise Password Safe.</para> + stronger encryption or delegating the storage of the key to an Enterprise Password Safe.</para> </section> </section> |