March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13059) org.apache.ws.security exports Jasypt

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13059?page=com.atlassian.jira.plugi... ] Jim Ma edited comment on WFLY-13059 at 3/16/20 6:24 AM: -------------------------------------------------------- [~pmm] I think this would be good that we provide a dedicated module for Jasypt and still export to ws security module. This will allow the old application with jbossws-cxf-client module dependency added can still access jasypt classes. If other application likes yours doesn't want this jasypt export dependency , it can be excluded with one line exclusion config in jboss-deployment-structure.xml. was (Author: jim.ma): [~pmm] I think this would be good if we provide a dedicated module for Jasypt and still export to ws security module. This will allow the application with jbossws-cxf-client module dependency can still access jasypt classes. If other the application likes yours doesn't want this jasypt export dependency , it can be excluded with one line exclusion config in jboss-deployment-structure.xml. > org.apache.ws.security exports Jasypt > ------------------------------------- > > Key: WFLY-13059 > URL: https://issues.redhat.com/browse/WFLY-13059 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Philippe Marschall > Assignee: Jim Ma > Priority: Major > > The {{org.apache.ws.security}} module contains the Jasypt JAR and exports it. Jasypt is only used internally by {{org.apache.wss4j.common.crypto.JasyptPasswordEncryptor}} and not used externally. > Our application has a dependency on {{org.jboss.ws.cxf.jbossws-cxf-client}} which has an exported dependency on {{org.apache.ws.security}} which exports Jasypt. As a consequence the Jasypt from the {{org.apache.ws.security}} module is used instead of the Jasypt from our application. > We would be willing to work on a patch. We see two possible options: > # Introduce a dedicated Jasypt module and make {{org.apache.ws.security}} depend on it without exporting it > # Add a resource filter to the {{org.apache.ws.security}} module like this {code} > <exports> > <exclude path="org/jasypt/**"/> > </exports> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-266) log4j2-jboss-logmanager LevelTranslator NullPointer

by Boris Unckel (Jira)

Boris Unckel created LOGMGR-266: ----------------------------------- Summary: log4j2-jboss-logmanager LevelTranslator NullPointer Key: LOGMGR-266 URL: https://issues.redhat.com/browse/LOGMGR-266 Project: JBoss Log Manager Issue Type: Bug Reporter: Boris Unckel We found the following Nullpointer Exception Caused by: java.lang.NullPointerException at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95) at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156) .... Reason seems that LevelTranslator is not defensive enough. Suggestion: java.util.logging.Level translateLevel(final Level level) { //level null is same as level not translated if(level == null) { return org.jboss.logmanager.Level.INFO; } final java.util.logging.Level result = log4jToJul.get(level.intLevel()); return result == null ? org.jboss.logmanager.Level.INFO : result; } Level translateLevel(final java.util.logging.Level level) { //level null is same as level not translated if(level == null) { return Level.INFO; } final Level result = julToLog4j.get(level.intValue()); return result == null ? Level.INFO : result; } -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13059) org.apache.ws.security exports Jasypt

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13059?page=com.atlassian.jira.plugi... ] Jim Ma edited comment on WFLY-13059 at 3/16/20 6:16 AM: -------------------------------------------------------- [~pmm] I think this would be good if we provide a dedicated module for Jasypt and still export to ws security module. This will allow the application with jbossws-cxf-client module dependency can still access jasypt classes. If other the application likes yours doesn't want this jasypt export dependency , it can be excluded with one line exclusion config in jboss-deployment-structure.xml. was (Author: jim.ma): [~pmm] Sorry for the long delay. Did you try to provide a jboss-deployment-structure.xml to exclude org.apache.ws.security module and add all the jars you need in application ? > org.apache.ws.security exports Jasypt > ------------------------------------- > > Key: WFLY-13059 > URL: https://issues.redhat.com/browse/WFLY-13059 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Philippe Marschall > Assignee: Jim Ma > Priority: Major > > The {{org.apache.ws.security}} module contains the Jasypt JAR and exports it. Jasypt is only used internally by {{org.apache.wss4j.common.crypto.JasyptPasswordEncryptor}} and not used externally. > Our application has a dependency on {{org.jboss.ws.cxf.jbossws-cxf-client}} which has an exported dependency on {{org.apache.ws.security}} which exports Jasypt. As a consequence the Jasypt from the {{org.apache.ws.security}} module is used instead of the Jasypt from our application. > We would be willing to work on a patch. We see two possible options: > # Introduce a dedicated Jasypt module and make {{org.apache.ws.security}} depend on it without exporting it > # Add a resource filter to the {{org.apache.ws.security}} module like this {code} > <exports> > <exclude path="org/jasypt/**"/> > </exports> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5165) Align docs to the new Maven related scripts without new user

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-5165: ------------------------------------------ Summary: Align docs to the new Maven related scripts without new user Key: DROOLS-5165 URL: https://issues.redhat.com/browse/DROOLS-5165 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1081) Automate Sidecar error: https://github.com/kiali/kiali/pull/2468

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1081?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1081: ---------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #36) > Automate Sidecar error: https://github.com/kiali/kiali/pull/2468 > ---------------------------------------------------------------- > > Key: SWSQE-1081 > URL: https://issues.redhat.com/browse/SWSQE-1081 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1090) Automate Sidecar validations

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1090?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1090: ---------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #36) > Automate Sidecar validations > ---------------------------- > > Key: SWSQE-1090 > URL: https://issues.redhat.com/browse/SWSQE-1090 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1687 > https://github.com/kiali/kiali/pull/2500 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1089) Remove hardcoded waiting for webhook "smcp.validation.maistra.io"

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1089?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1089: ---------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #36) > Remove hardcoded waiting for webhook "smcp.validation.maistra.io" > ----------------------------------------------------------------- > > Key: SWSQE-1089 > URL: https://issues.redhat.com/browse/SWSQE-1089 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Optional > Labels: infrastructure > > https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... > There is no need to wait that long. We need some dynamic check. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1083) Automate Tracing link: https://github.com/kiali/kiali/issues/2479

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1083?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1083: ---------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #36) > Automate Tracing link: https://github.com/kiali/kiali/issues/2479 > ----------------------------------------------------------------- > > Key: SWSQE-1083 > URL: https://issues.redhat.com/browse/SWSQE-1083 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1077: ---------------------------------- Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #32, Kiali Sprint #36) > Kiali Test For Istio.io > ----------------------- > > Key: SWSQE-1077 > URL: https://issues.redhat.com/browse/SWSQE-1077 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal. > Meeting with [~brian.avery] [~gbaufake]: > 1) BrianA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework > https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te... > 2) Kiali team then to add an api test case(s) via 'curl' to validate the Istio/Kiali integration is properly functioning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1056) Try OCP 4.4 on IPv6 in PSI

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1056?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1056: ---------------------------------- Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #30 (was: Kiali Sprint #32, Kiali Sprint #36) > Try OCP 4.4 on IPv6 in PSI > -------------------------- > > Key: SWSQE-1056 > URL: https://issues.redhat.com/browse/SWSQE-1056 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 March 2020