Massimo Paladin created AMQ-4133:
------------------------------------
Summary: Different behaviour with similar connectors with
identical option, URI validation would be nice to have
Key: AMQ-4133
URL: https://issues.apache.org/jira/browse/AMQ-4133
Project: ActiveMQ
Issue Type: Bug
Reporter: Massimo Paladin
Hello,
we noticed an inconsistent behaviour of stomp+ssl and stomp+nio+ssl with same
connector options.
- stomp+ssl works with both {{transport.needClientAuth=true}} and
{{needClientAuth=true}} options
- stomp+nio+ssl works with {{transport.needClientAuth=true}} but not with
{{needClientAuth=true}}
In this last case it fails with a non-obvious exception:
{noformat}
junit.framework.ComparisonFailure: java.lang.SecurityException: Unable to
authenticate transport without SSL certificate.
at
org.apache.activemq.security.JaasCertificateAuthenticationBroker.addConnection(JaasCertificateAuthenticationBroker.java:74)
at
org.apache.activemq.security.JaasDualAuthenticationBroker.addConnection(JaasDualAuthenticationBroker.java:98)
{noformat}
It would be nice to have a URI parameters validation or the same behaviour with
similar connectors.
What do you think?
Unit test which shows the problem attached, sorry for reusing pieces from
another bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
