Hello Lorenz,
Yes, I think there is a misunderstanding here. In our tests, we activated SSL and SASL and the messages were successfully sent/received and were encrypted. Is the above in contradiction with what is said here "the AMQP 1.0 Qpid JMS Client does currently not support message encryption"? Regards, Adel ________________________________ From: Lorenz Quack <[email protected]> Sent: Tuesday, December 6, 2016 1:46:19 PM To: [email protected] Subject: Re: [Qpid Java Broker 6.0.4] Java Cryptography Extension Hello Adel, As mentioned by Keith, the AMQP 1.0 Qpid JMS Client does currently not support message encryption. Or did I misunderstand your follow-up question? Furthermore, the Kerberos AuthenticationProvider also requires the full strength JCE. Kind regards, Lorenz On 06/12/16 09:13, Adel Boutros wrote: > Thank you Keith! > > > For AMQP 1.0 Qpid JMS , what encryption mechanism is used? > > > Regards, > > Adel > > ________________________________ > From: Keith W <[email protected]> > Sent: Tuesday, December 6, 2016 10:00:47 AM > To: [email protected] > Subject: Re: [Qpid Java Broker 6.0.4] Java Cryptography Extension > > Hi Adel > > Within the Qpid Broker for Java, it is the Configuration Encryption piece: > > https://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Security-Configuration-Encryption.html > > The 0-8..0-10 Qpid JMS client also uses the JCE for end to end message > payload/header encryption. > > https://qpid.apache.org/releases/qpid-java-6.1.0/jms-client-0-8/book/JMS-Client-Message-Encryption.html > > The newer AMQP 1.0 Qpid JMS Client does not support this feature (yet). > > Kind regards, Keith Wall. > > > > On 6 December 2016 at 08:35, Adel Boutros <[email protected]> wrote: >> Hello, >> >> >> It is mentioned in the link below that some features require Java >> Cryptography Extension. What are those features exactly? >> >> >> http://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Installation-Prerequistes.html#ftn.d0e103 >> >> >> Regards, >> >> Adel > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
