December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFCORE-5221) SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFCORE-5221?page=com.atlassian.jira.plug... ] Fabio Burzigotti updated WFCORE-5221: ------------------------------------- Fix Version/s: (was: 7.0.0.Alpha5) (was: 7.0.0.Final) > SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL > ------------------------------------------------------------- > > Key: WFCORE-5221 > URL: https://issues.redhat.com/browse/WFCORE-5221 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > SNICombinedWithALPNTestCase added with WFCORE-3873 does not conform with IBM JDK key algorithm name. This needs to be fixed. > Also as IBM JDK 8 and lower does not contain ALPN implementation and neither the ALPN-hack work there (it works only with Oracle JDK and Open JDK as it depends on JDK internals) we would have to provide ALPN in such situation somehow. We can either use Jetty ALPN implementation or wildfly-openssl using OpenSSL libraries. Both variants would bring unwanted difficulties with running this testsuite in our environment. > Let's skip these tests for IBM JDK less than version 9. With newer IBM JDK version, there will probably be ALPN already part of JDK, so we can execute it then. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5221) SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFCORE-5221?page=com.atlassian.jira.plug... ] Fabio Burzigotti updated WFCORE-5221: ------------------------------------- Affects Version/s: (was: 7.0.0.Final) > SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL > ------------------------------------------------------------- > > Key: WFCORE-5221 > URL: https://issues.redhat.com/browse/WFCORE-5221 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Reporter: Fabio Burzigotti > Assignee: Jan Stourac > Priority: Major > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > SNICombinedWithALPNTestCase added with WFCORE-3873 does not conform with IBM JDK key algorithm name. This needs to be fixed. > Also as IBM JDK 8 and lower does not contain ALPN implementation and neither the ALPN-hack work there (it works only with Oracle JDK and Open JDK as it depends on JDK internals) we would have to provide ALPN in such situation somehow. We can either use Jetty ALPN implementation or wildfly-openssl using OpenSSL libraries. Both variants would bring unwanted difficulties with running this testsuite in our environment. > Let's skip these tests for IBM JDK less than version 9. With newer IBM JDK version, there will probably be ALPN already part of JDK, so we can execute it then. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5221) SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFCORE-5221?page=com.atlassian.jira.plug... ] Fabio Burzigotti reassigned WFCORE-5221: ---------------------------------------- Assignee: (was: Jan Stourac) > SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL > ------------------------------------------------------------- > > Key: WFCORE-5221 > URL: https://issues.redhat.com/browse/WFCORE-5221 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Reporter: Fabio Burzigotti > Priority: Major > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > SNICombinedWithALPNTestCase added with WFCORE-3873 does not conform with IBM JDK key algorithm name. This needs to be fixed. > Also as IBM JDK 8 and lower does not contain ALPN implementation and neither the ALPN-hack work there (it works only with Oracle JDK and Open JDK as it depends on JDK internals) we would have to provide ALPN in such situation somehow. We can either use Jetty ALPN implementation or wildfly-openssl using OpenSSL libraries. Both variants would bring unwanted difficulties with running this testsuite in our environment. > Let's skip these tests for IBM JDK less than version 9. With newer IBM JDK version, there will probably be ALPN already part of JDK, so we can execute it then. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5221) SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL

by Fabio Burzigotti (Jira)

Fabio Burzigotti created WFCORE-5221: ---------------------------------------- Summary: SNICombinedWithALPNTestCase fails with Oracle JDK 1.8 on RHEL Key: WFCORE-5221 URL: https://issues.redhat.com/browse/WFCORE-5221 Project: WildFly Core Issue Type: Bug Components: Security, Test Suite Affects Versions: 7.0.0.Final Reporter: Fabio Burzigotti Assignee: Jan Stourac Fix For: 7.0.0.Alpha5, 7.0.0.Final SNICombinedWithALPNTestCase added with WFCORE-3873 does not conform with IBM JDK key algorithm name. This needs to be fixed. Also as IBM JDK 8 and lower does not contain ALPN implementation and neither the ALPN-hack work there (it works only with Oracle JDK and Open JDK as it depends on JDK internals) we would have to provide ALPN in such situation somehow. We can either use Jetty ALPN implementation or wildfly-openssl using OpenSSL libraries. Both variants would bring unwanted difficulties with running this testsuite in our environment. Let's skip these tests for IBM JDK less than version 9. With newer IBM JDK version, there will probably be ALPN already part of JDK, so we can execute it then. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5888) Comments starting with ruletable without a space should work

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5888?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-5888: -------------------------------------- Fix when needed is here [Rikkola/drools at DROOLS-5888-ruletable-fix (github.com)|https://github.com/Rikkola/drools/tree/DROOLS-5888-ruletable-fix] > Comments starting with ruletable without a space should work > ------------------------------------------------------------ > > Key: DROOLS-5888 > URL: https://issues.redhat.com/browse/DROOLS-5888 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > A column description "ruletablesomething" is considered as a start of a new dtable, but as rare it is this should work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5888) Comments starting with ruletable without a space should work

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5888: ------------------------------------ Summary: Comments starting with ruletable without a space should work Key: DROOLS-5888 URL: https://issues.redhat.com/browse/DROOLS-5888 Project: Drools Issue Type: Bug Components: XLS Decision Table Editor Reporter: Toni Rikkola Assignee: Toni Rikkola A column description "ruletablesomething" is considered as a start of a new dtable, but as rare it is this should work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5041) The public elytron module exports private API

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5041?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on WFCORE-5041: ------------------------------------------ I believe the main issue here was the presence of the export="true" attribute in addition to the individually listed exports, by adding export=true everything is exported not just the filtered list. > The public elytron module exports private API > --------------------------------------------- > > Key: WFCORE-5041 > URL: https://issues.redhat.com/browse/WFCORE-5041 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Priority: Major > > The public elytron module is defined as: > {code:xml} > <module name="org.wildfly.security.elytron-private" services="export" export="true"> > <exports> > <include-set> > <path name="org/wildfly/security"/> > {code} > The issue is export="true" exports everything including the private API. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron

by Alessandro Moscatelli (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Alessandro Moscatelli edited comment on WFLY-14189 at 12/9/20 5:48 AM: ----------------------------------------------------------------------- Also, I confirm that when replacing RolesAllowed with PermitAll everything is ok, just like for issue 9039. I also searched for simular issue related to PostConstruct and Elytron and found nothing. All I could find is 7936, but it's related to Servlets : WFLY-7936 The RunAs annotation doesn't work in servlets with Elytron - Red Hat Issue Tracker Thank you advance was (Author: alessandromoscatelli): Also, I confirm that using @PermitAll works, just like for issue 9039. I also searched for simular issue related to PostConstruct and Elytron and found nothing. All I could find is 7936, but it's related to Servlets : [WFLY-7936] The RunAs annotation doesn't work in servlets with Elytron - Red Hat Issue Tracker Thank you advance > The RunAs annotation doesn't work in EJBs with Elytron > ------------------------------------------------------ > > Key: WFLY-14189 > URL: https://issues.redhat.com/browse/WFLY-14189 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: standalone-full-ha.new.xml, test.zip > > > Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. > Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain. > This exception is rised when deploying the application. > Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) > Test/Sample project: [^test.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron

by Alessandro Moscatelli (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Alessandro Moscatelli commented on WFLY-14189: ---------------------------------------------- Also, I confirm that using @PermitAll works, just like for issue 9039. I also searched for simular issue related to PostConstruct and Elytron and found nothing. All I could find is 7936, but it's related to Servlets : [WFLY-7936] The RunAs annotation doesn't work in servlets with Elytron - Red Hat Issue Tracker Thank you advance > The RunAs annotation doesn't work in EJBs with Elytron > ------------------------------------------------------ > > Key: WFLY-14189 > URL: https://issues.redhat.com/browse/WFLY-14189 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: standalone-full-ha.new.xml, test.zip > > > Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. > Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain. > This exception is rised when deploying the application. > Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) > Test/Sample project: [^test.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFWIP-366) MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-366?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFWIP-366: ------------------------------------ > Are you sure these tests ever pass with -Dts.bootable on nightly runs? You are right. I was tricked by green ball, but did not checked if test was really run. Now I did and test is really not run in nightly. Sorry for that false statement. Yesterday when I was reviewing MR I came to similar conclusion as you did. > MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run > ------------------------------------------------------------------------------------------------------------ > > Key: WFWIP-366 > URL: https://issues.redhat.com/browse/WFWIP-366 > Project: WildFly WIP > Issue Type: Bug > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > {code} > cd testsuite/integration/microprofile > mvn test -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase > ... > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401> > [ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true > cleanInit=true > overallResponseCode=401 > overallSawVendor=false > scopedResponseCode=401 > scopedSawVendor=false > expected:<[200]> but was:<[401]> > [INFO] > [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 > {code} > Looking into tested bootable jar It seems strange I still see security-enabled="false" > {code} > <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/> > {code} > Management interface is secured > {code} > <management-interfaces> > <http-interface http-authentication-factory="management-http-authentication"> > <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/> > <socket-binding http="management-http"/> > </http-interface> > </management-interfaces> > {code} > But mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword" > Same test is passing in WF22 nightly runs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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