October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11200) Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFLY-11200?page=com.atlassian.jira.plugin... ] Petr Kremensky edited comment on WFLY-11200 at 10/18/18 9:25 AM: ----------------------------------------------------------------- WFLY-9096 should be reverted as it forces client to use "TLSv1,TLSv1.1,TLSv1.2". {noformat} Oracle 1.8.0_181 engine.getEnabledProtocols() result = {String[4]@5733} 0 = "SSLv2Hello" 1 = "TLSv1" 2 = "TLSv1.1" 3 = "TLSv1.2" IBM 1.8.0_181 engine.getEnabledProtocols() result = {String[1]@2017} 0 = "TLSv1" {noformat} client running on IBM has different set of protocols enabled. Test mentioned in WFLY-9096 should be fixed by either enabling TLSv1 on server, or adding -Dcom.ibm.jsse2.overrideDefaultTLS=true property to client (tested the other option now, and work as expected). This should be also documented. was (Author: pkremens): WFLY-9096 should be reverted as it forces client to use "TLSv1,TLSv1.1,TLSv1.2". {noformat} Oracle 1.8.0_181 engine.getEnabledProtocols() result = {String[4]@5733} 0 = "SSLv2Hello" 1 = "TLSv1" 2 = "TLSv1.1" 3 = "TLSv1.2" IBM 1.8.0_181 engine.getEnabledProtocols() result = {String[1]@2017} 0 = "TLSv1" {noformat} client running on IBM has different set of protocols enabled. Test mentioned in WFLY-9096 should be fixed by either enabling TLSv1 on server, or adding -Dcom.ibm.jsse2.overrideDefaultTLS=true property to client. This should be also documented. > Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-11200 > URL: https://issues.jboss.org/browse/WFLY-11200 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > > Integration code of messaging-activemq sets enabledProtocols=\["TLSv1,TLSv1.1,TLSv1.2"\] property to NettyConnector lookedup by the client. This behaviour was introduced by WFLY-9096 (https://github.com/wildfly/wildfly/pull/11673/files). > https://github.com/wildfly/wildfly/pull/11673/files#diff-64b7f8a3e5eb2234... > {code} > parameters.putIfAbsent(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, "TLSv1,TLSv1.1,TLSv1.2"); > {code} > https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... > {code} > enabledProtocols = ConfigurationHelper.getStringProperty(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, TransportConstants.DEFAULT_ENABLED_PROTOCOLS, configuration); > {code} > NettyConnector prefers the enabled protocols obtained from integration code to ones defined on client side - possibly forces client to use less secured protocol than client wants. > https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... > {code} > ... > String[] originalProtocols = engine.getEnabledProtocols(); > ... > if (enabledProtocols != null) { // true with WFLY-9096 > try { > engine.setEnabledProtocols(SSLSupport.parseCommaSeparatedListIntoArray(enabledProtocols)); > } catch (IllegalArgumentException e) { > ActiveMQClientLogger.LOGGER.invalidProtocol(SSLSupport.parseArrayIntoCommandSeparatedList(engine.getSupportedProtocols())); > throw e; > } > } else { > engine.setEnabledProtocols(originalProtocols); > } > ... > {code} > *Reproduce* > {code:bash} > WORKSPACE=`pwd` > WILDFLY=${WORKSPACE}/wildfly > TESTSUITE=${WORKSPACE}/eap-tests-hornetq > SERVERS=${WORKSPACE}/servers > export JBOSS_HOME_1=${SERVERS}/server1/jboss-eap > export JBOSS_HOME_2=${SERVERS}/server2/jboss-eap > export JBOSS_HOME_3=${SERVERS}/server3/jboss-eap > export JBOSS_HOME_4=${SERVERS}/server4/jboss-eap > # setup testing server > cd $WORKSPACE > git clone git@github.com:wildfly/wildfly.git > cd $WILDFLY > mvn clean install -DskipTests -pl dist -am > cd dist/target > zip -r /tmp/wildfly.zip wildfly-*-SNAPSHOT > # setup testsuite > cd $WORKSPACE > git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git > mkdir $SERVERS > cd $SERVERS > groovy -DEAP_ZIP_URL=file:///tmp/wildfly.zip ${TESTSUITE}/scripts/PrepareServers7.groovy > # run the reproducer > cd $TESTSUITE/jboss-hornetq-testsuite > mvn clean test -Dtest=ElytronSslAuthenticationTestCase#testOneWaySslOverSSLv3Jms -pl tests-eap7 -am > {code} > *Test details:* > *server* supports TLSv1.1 > {code:xml} > <server-ssl-contexts> > <server-ssl-context name="server-ssl-context" protocols="TLSv1.1" need-client-auth="false" key-manager="key-manager-name_server-ssl-context"/> > </server-ssl-contexts> > {code} > *client* is forced (byteman rule) to use the SSLv3 > *Actual:* > Connection is made. > *Expected:* > javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11200) Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFLY-11200?page=com.atlassian.jira.plugin... ] Petr Kremensky commented on WFLY-11200: --------------------------------------- WFLY-9096 should be reverted as it forces client to use "TLSv1,TLSv1.1,TLSv1.2". {noformat} Oracle 1.8.0_181 engine.getEnabledProtocols() result = {String[4]@5733} 0 = "SSLv2Hello" 1 = "TLSv1" 2 = "TLSv1.1" 3 = "TLSv1.2" IBM 1.8.0_181 engine.getEnabledProtocols() result = {String[1]@2017} 0 = "TLSv1" {noformat} client running on IBM has different set of protocols enabled. Test mentioned in WFLY-9096 should be fixed by either enabling TLSv1 on server, or adding -Dcom.ibm.jsse2.overrideDefaultTLS=true property to client. This should be also documented. > Messaging-activemq integration code alters the JMS client's enabled protocols via TransportConfiguration > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-11200 > URL: https://issues.jboss.org/browse/WFLY-11200 > Project: WildFly > Issue Type: Bug > Components: JMS, Security > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Major > > Integration code of messaging-activemq sets enabledProtocols=\["TLSv1,TLSv1.1,TLSv1.2"\] property to NettyConnector lookedup by the client. This behaviour was introduced by WFLY-9096 (https://github.com/wildfly/wildfly/pull/11673/files). > https://github.com/wildfly/wildfly/pull/11673/files#diff-64b7f8a3e5eb2234... > {code} > parameters.putIfAbsent(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, "TLSv1,TLSv1.1,TLSv1.2"); > {code} > https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... > {code} > enabledProtocols = ConfigurationHelper.getStringProperty(TransportConstants.ENABLED_PROTOCOLS_PROP_NAME, TransportConstants.DEFAULT_ENABLED_PROTOCOLS, configuration); > {code} > NettyConnector prefers the enabled protocols obtained from integration code to ones defined on client side - possibly forces client to use less secured protocol than client wants. > https://github.com/apache/activemq-artemis/blob/2.6.3/artemis-core-client... > {code} > ... > String[] originalProtocols = engine.getEnabledProtocols(); > ... > if (enabledProtocols != null) { // true with WFLY-9096 > try { > engine.setEnabledProtocols(SSLSupport.parseCommaSeparatedListIntoArray(enabledProtocols)); > } catch (IllegalArgumentException e) { > ActiveMQClientLogger.LOGGER.invalidProtocol(SSLSupport.parseArrayIntoCommandSeparatedList(engine.getSupportedProtocols())); > throw e; > } > } else { > engine.setEnabledProtocols(originalProtocols); > } > ... > {code} > *Reproduce* > {code:bash} > WORKSPACE=`pwd` > WILDFLY=${WORKSPACE}/wildfly > TESTSUITE=${WORKSPACE}/eap-tests-hornetq > SERVERS=${WORKSPACE}/servers > export JBOSS_HOME_1=${SERVERS}/server1/jboss-eap > export JBOSS_HOME_2=${SERVERS}/server2/jboss-eap > export JBOSS_HOME_3=${SERVERS}/server3/jboss-eap > export JBOSS_HOME_4=${SERVERS}/server4/jboss-eap > # setup testing server > cd $WORKSPACE > git clone git@github.com:wildfly/wildfly.git > cd $WILDFLY > mvn clean install -DskipTests -pl dist -am > cd dist/target > zip -r /tmp/wildfly.zip wildfly-*-SNAPSHOT > # setup testsuite > cd $WORKSPACE > git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git > mkdir $SERVERS > cd $SERVERS > groovy -DEAP_ZIP_URL=file:///tmp/wildfly.zip ${TESTSUITE}/scripts/PrepareServers7.groovy > # run the reproducer > cd $TESTSUITE/jboss-hornetq-testsuite > mvn clean test -Dtest=ElytronSslAuthenticationTestCase#testOneWaySslOverSSLv3Jms -pl tests-eap7 -am > {code} > *Test details:* > *server* supports TLSv1.1 > {code:xml} > <server-ssl-contexts> > <server-ssl-context name="server-ssl-context" protocols="TLSv1.1" need-client-auth="false" key-manager="key-manager-name_server-ssl-context"/> > </server-ssl-contexts> > {code} > *client* is forced (byteman rule) to use the SSLv3 > *Actual:* > Connection is made. > *Expected:* > javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11199) Upgrade WildFly Core 7.0.0.Alpha4

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11199?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-11199: ------------------------------- Summary: Upgrade WildFly Core 7.0.0.Alpha4 (was: Upgrade WildFly Core 7.0.0.Alpha3) > Upgrade WildFly Core 7.0.0.Alpha4 > --------------------------------- > > Key: WFLY-11199 > URL: https://issues.jboss.org/browse/WFLY-11199 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) Scenario UX/Visual enhancements

by Ivo Bek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-3126: ---------------------------- Epic Name: Scenario UX/Visual enhancements > Scenario UX/Visual enhancements > ------------------------------- > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > *Contextual menus & pop-overs* > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3110: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, a2.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. > h2. Another steps to reproduce > Run the code snippet below > {code:java} > final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() ); > final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" ); > assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) ); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3110: ---------------------------------------- [~karreiro] Could you please take a look? [~tari_manga] Any ideas (from the DMN file and server log)? > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, a2.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. > h2. Another steps to reproduce > Run the code snippet below > {code:java} > final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() ); > final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" ); > assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) ); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3110: -------------------------------- Description: I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. h2. Another steps to reproduce Run the code snippet below {code:java} final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() ); final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" ); assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) ); {code} was:I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, a2.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. > h2. Another steps to reproduce > Run the code snippet below > {code:java} > final DMNRuntime runtime = DMNRuntimeUtil.createRuntime("a2.dmn", this.getClass() ); > final DMNModel dmnModel = runtime.getModel("https://github.com/kiegroup/drools/kie-dmn", "a2" ); > assertThat( DMNRuntimeUtil.formatMessages( dmnModel.getMessages() ), dmnModel.hasErrors(), is( false ) ); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3110: -------------------------------- Attachment: a2.dmn > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, a2.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3110: ------------------------------------- [~manstis] setting this as blocker, because basically can not try runtime with any PR. > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3110) [DMN Designer] Unable to deploy model with custom data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3110?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3110: -------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Unable to deploy model with custom data type > ----------------------------------------------------------- > > Key: DROOLS-3110 > URL: https://issues.jboss.org/browse/DROOLS-3110 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: a1.dmn, error.log > > > I created the [^a1.dmn] model using features of DROOLS-3024, however then I am not able to deploy the created dmn model, the attached [^error.log] appears in server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018