Re: Mutual SSL authentication with Camel applications
Hi Have you tried the AMQ forum to see if there is a solution that works with AMQ only? Then we know its possible and can see if there is something needed to be changed in camel-jms or maybe in the activemq-camel component that is shipped with AMQ itself. On Fri, Mar 13, 2009 at 7:39 AM, huntc hu...@mac.com wrote: By the way, here are some of the things I'm observing when attempting mutual authentication: 1. Wireshark shows: Client Hello Server Hello, Certificate, Certificate Request, Server Hello Done Certificate, Client Key Exchange Alert (Level: Fatal, Description: Bad Certificate) If I look at the Certificate, Client Key Exchange in detail I see in the Handshake Protocol: Certificate that the Certificates Length is 0. 2. ActiveMQ shows in its log: ERROR TransportConnector - Could not accept connection : null cert chain I'm presuming that this is because the client has not passed its certificate. I hope that these are useful observations. -- View this message in context: http://www.nabble.com/Mutual-SSL-authentication-with-Camel-applications-tp22490614p22491057.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
Re: StreamCaching in Camel 1.6
On Fri, Mar 6, 2009 at 1:46 PM, _Jens jens.riemschnei...@icw.de wrote:
Hi,
first of all, thanks to both of you, Gert and Willem, for the quick replies.
I saw that the jira was already fixed, great job.
Does this mean that the methods for disabling stream caching will be removed
in the future?
I have tried to use noErrorHandler but there was a special case that used
the default error handler at some point and I wasn't able to change this. A
drilled down version of my scenario is shown in the test case below.
It has to do with the choice and when elements in the route. They seem to
introduce the standard error handler, as they don't inherit the configured
one. The standard error handling then configures the route to use stream
caching again. For some reason this only seems to happen if the JMX agent is
disabled in the CamelContext, which I simulate by setting the system
property. Of course, in our real scenario we simply disable it in the
application context.
So you are saying that with/without JMX it has an influence on your route?
That is kinda odd, but there could be a gremlin.
Need to check into this.
�...@test
public void testUploadFailsForBigFileWithNoErrorHandler() throws
Exception {
System.setProperty(JmxSystemPropertyKeys.DISABLED, true);
DefaultCamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
�...@override
public void configure() throws Exception {
errorHandler(noErrorHandler());
from(jetty:http://localhost:8989/bigfile;)
.choice().when(header(foo).isEqualTo(bar)).to(direct:end)
.otherwise().end();
from(direct:end)
.process(new Processor() {
public void process(Exchange exchange) throws
Exception {
InputStream inputStream =
exchange.getIn().getBody(InputStream.class);
while (inputStream.read() != -1) {}
}
});
}
});
context.start();
HttpClient client = new HttpClient();
PostMethod method = new PostMethod(http://localhost:8989/bigfile;);
File file = new File(c:\\temp\\test.bin.ok2);
method.setRequestEntity(new FileRequestEntity(file,
unknown/unknown));
assertEquals(200, client.executeMethod(method));
}
--
View this message in context:
http://www.nabble.com/StreamCaching-in-Camel-1.6-tp22305654p22371815.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: StreamCaching in Camel 1.6
Hi Claus, yes, it seems to have an effect because the lifecycle-strategy is different when disabling JMX. The Constructor of the DefaultCamelContext uses either DefaultLifecycleStrategy or InstrumentationLifecycleStrategy. This also has influence on the error handling strategy. Jens -- View this message in context: http://www.nabble.com/StreamCaching-in-Camel-1.6-tp22305654p22554404.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: Mutual SSL authentication with Camel applications
Hi Claus, Thanks for your reply. I forgot that I made this posting otherwise I would have sent through an update. I did post to the AMQ forum and then discovered for myself what the problem was - the java client consuming the services needed authenticated access to its keystore. I'm going to write a blog entry on securing AMQ very shortly as it is a thinly covered topic which I think I now have experienced pretty well. Kind regards, Christopher -- View this message in context: http://www.nabble.com/Mutual-SSL-authentication-with-Camel-applications-tp22490614p22554822.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: Mutual SSL authentication with Camel applications
Here's the promised blog entry: http://christopherhunt-software.blogspot.com/2009/03/mutual-ssl-authentication-and-ldap.html -- View this message in context: http://www.nabble.com/Mutual-SSL-authentication-with-Camel-applications-tp22490614p22558460.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
[ANN] Apache Camel 2.0-M1 released
The Camel team is pleased to announce the first milestone release of the improved Apache Camel [1], version 2.0-M1. This version features a record 368 issues fixed including: - New examples - New EIP: Sort - New components: cometd, freemarker, restlet, rss - New DataFormats: json, zip, bindy - New Languages: Mven, Property - New annotations - improvements to many component like: File, HTTP, Jetty, MINA, CXF, JMS - API and DSL cleanup - ... and much more Please see the Release Notes [2] for more details: [1] http://camel.apache.org/ [2] http://camel.apache.org/camel-20-m1-release.html Enjoy, The Camel riders
