May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13511) CVE-2020-1695: resteasy-jaxrs-3.11.2

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13511?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13511: ------------------------------------ Security: (was: Security Issue) > CVE-2020-1695: resteasy-jaxrs-3.11.2 > ------------------------------------ > > Key: WFLY-13511 > URL: https://issues.redhat.com/browse/WFLY-13511 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Affects Versions: 19.0.0.Final, 19.1.0.Final > Reporter: Radoslav Ivanov > Assignee: Ronald Sigal > Priority: Critical > Fix For: 20.0.0.Beta1 > > > Please fix High prio CVE-2020-1695 vulnerability issue with JAXRS: > {code:java} > File Path org\jboss\resteasy\resteasy-jaxrs\3.11.0.Final\resteasy-jaxrs-3.11.0.Final.jar > SHA-1 e0a65cedf19500c87a0539980835940806438efb > SHA-256 3d87cd378ae039ade28e9988611a86f5732d713942ecf8ed594909281ba3064b > Description A flaw was found in all resteasy 3.x.x versions prior to 3.12.0.Final and all resteasy 4.x.x versions prior to 4.6.0.Final, where an improper input validation results in returning an illegal header that integrates into the server's response. This flaw may result in an injection, which leads to unexpected behavior when the HTTP response is constructed. > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5379) Add more accumulate tests

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5379?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-5379: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Luca Molteni) > Add more accumulate tests > ------------------------- > > Key: DROOLS-5379 > URL: https://issues.redhat.com/browse/DROOLS-5379 > Project: Drools > Issue Type: Sub-task > Components: executable model > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Add more accumulate tests for stability. Especially, variants of testAccumulateOnStaticMethod(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5379) Add more accumulate tests

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5379: ----------------------------------------- Summary: Add more accumulate tests Key: DROOLS-5379 URL: https://issues.redhat.com/browse/DROOLS-5379 Project: Drools Issue Type: Sub-task Components: executable model Affects Versions: 7.38.0.Final Reporter: Toshiya Kobayashi Assignee: Luca Molteni Add more accumulate tests for stability. Especially, variants of testAccumulateOnStaticMethod(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-12835: ------------------------------------ I still think this is a feature request. MicroProfile does not specify anything related to EAR deployments so it's up to us (WildFly) to decide what is supported or not. It used to work in WildFly 16 by chance but the fix for WFLY-12811 highlighted that injecting Config property in a health check in a WAR deployment was not working. This use case is covered by MicroProfile so I changed the behaviour. As Charles is mentioning in his PR, the tricky part is not really MP Health but MP Config. When a EAR is having a health check in a subdeployment, where the MP Config property values come from? In the current codebase, each deployment have their own instance of Config that is bound to the deployment's module class loader. This does not align with EAR class loader mechanism as the WAR deployment will not use Config Source provided by a library JAR in the EAR. I'm fine with supporting EAR with the following caveats: * MicroProfile Health Checks that uses injected config properties MUST provide the property values in the same sub deployment (i.e. providing a JAR library to provide config property values to multiple subdeployments is still not supported) * MicroProfile Health Checks names must be unique across subdeployments > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13353) Add a Galleon layer for the POJO subsystem

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13353?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13353: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13235, https://github.com/wildfly/wildfly-proposals/pull/309 (was: https://github.com/wildfly/wildfly/pull/13235) > Add a Galleon layer for the POJO subsystem > ------------------------------------------ > > Key: WFLY-13353 > URL: https://issues.redhat.com/browse/WFLY-13353 > Project: WildFly > Issue Type: Feature Request > Components: Build System, POJO > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Optional > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13518) Bump messaging schema to 11

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13518: ---------------------------------------- Summary: Bump messaging schema to 11 Key: WFLY-13518 URL: https://issues.redhat.com/browse/WFLY-13518 Project: WildFly Issue Type: Enhancement Components: JMS, Management Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Bump messaging schema and model versions to 11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5364) Test scenario reports data type change during creation

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5364?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5364: -------------------------------- Description: There is warning about data type change even when a test scenario is just created. The spotted behavior would be expected if user is reopening a a scenario but not creating a new one. h2. Acceptance test https://github.com/jboss-integration/bxms-qe-tests/pull/3283 was: There is warning about data type change even when a test scenario is just created. The spotted behavior would be expected if user is reopening a a scenario but not creating a new one. > Test scenario reports data type change during creation > ------------------------------------------------------ > > Key: DROOLS-5364 > URL: https://issues.redhat.com/browse/DROOLS-5364 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.38.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-05-25 08-04-44.png, sample_abcd.zip > > > There is warning about data type change even when a test scenario is just created. The spotted behavior would be expected if user is reopening a a scenario but not creating a new one. > h2. Acceptance test > https://github.com/jboss-integration/bxms-qe-tests/pull/3283 > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13351) Add a Galleon layer for the Mail subsystem

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13351?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13351: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13233, https://github.com/wildfly/wildfly-proposals/pull/308 (was: https://github.com/wildfly/wildfly/pull/13233) > Add a Galleon layer for the Mail subsystem > ------------------------------------------ > > Key: WFLY-13351 > URL: https://issues.redhat.com/browse/WFLY-13351 > Project: WildFly > Issue Type: Feature Request > Components: Build System, Mail > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13128) Add a Galleon layer for batch-jberet

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13128?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13128: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13016 > Add a Galleon layer for batch-jberet > ------------------------------------ > > Key: WFLY-13128 > URL: https://issues.redhat.com/browse/WFLY-13128 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > I saw a community request for a Galleon layer for batch-jberet so let's make it first in the set we add to complete coverage of the various subsystems. > Besides the usual layer smoke tests, we can provision a cloud-server+batch-jberet server in testsuite/integration/basic and run most of the batch tests there against it. There are 4 that won't run because they use EJB, Agroal or the org.jboss.remoting3 module, none of which would be provisioned. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4983) Fix bootable jar failing tests

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4983: -------------------------------------------- Summary: Fix bootable jar failing tests Key: WFCORE-4983 URL: https://issues.redhat.com/browse/WFCORE-4983 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Jean Francois Denise Assignee: Jean Francois Denise 2 issues: * We have CLI script file duplication in testsuite/elytron that needs to be cleaned-up. * Test org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfacePKCS12TestCase needs to be excluded, depends on admin-mode. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 May 2020