[
https://issues.apache.org/jira/browse/QPID-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653499#comment-15653499
]
Lorenz Quack commented on QPID-7466:
------------------------------------
Hi,
I think :
* we should mention that in accordance with the spec the entities in the
distinguished name are ordered.
* in the example JNDI file we should have {{consumer1ConnectionFactory}} and
{{consumer2ConnectionFactory}} to indicate that each consumer should use a
different one with its own {{encryption_key_store}}. The example application
code would obviously have to change to refer to {{consumer1ConnectionFactory}}
instead of {{consumerConnectionFactory}}. I don't think we have to show code
using the second {{consumer2ConnectionFactory}}.
> [Java Broker, Java Client for AMQP 0-8 to 0-10] Improve documentation for
> end-to-end encryption
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-7466
> URL: https://issues.apache.org/jira/browse/QPID-7466
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker, Java Client
> Affects Versions: qpid-java-6.0, qpid-java-6.0.4, qpid-java-6.1
> Reporter: Lorenz Quack
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The documentation on end-to-end encryption is currently lacking in some areas
> and should be improved in at least the following ways:
> Client docs:
> * The special format for {{encryption_remote_trust_store}} in the connection
> URL is not well explained
> * This is complicated enough to warrant an example with config and code.
> Broker docs:
> * The {{exposedAsMessageSource}} on the {{TrustStore}} should be explained.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
