January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14261) Integrate MP Health 3.0 into EAP

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14261?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFLY-14261: ----------------------------------- Adding the merged-to-feature-branch label to indicate that this has been merged to https://github.com/wildfly/wildfly/tree/MP4 > Integrate MP Health 3.0 into EAP > -------------------------------- > > Key: WFLY-14261 > URL: https://issues.redhat.com/browse/WFLY-14261 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Labels: MP4.0, merged-to-feature-branch > > [Health 3.0|https://github.com/microprofile/microprofile-wg/issues/14] > [https://github.com/eclipse/microprofile-health/blob/master/spec/src/main/...] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14261) Integrate MP Health 3.0 into EAP

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14261?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-14261: ------------------------------ Labels: MP4.0 merged-to-feature-branch (was: MP4.0) > Integrate MP Health 3.0 into EAP > -------------------------------- > > Key: WFLY-14261 > URL: https://issues.redhat.com/browse/WFLY-14261 > Project: WildFly > Issue Type: Feature Request > Components: MP Health > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Labels: MP4.0, merged-to-feature-branch > > [Health 3.0|https://github.com/microprofile/microprofile-wg/issues/14] > [https://github.com/eclipse/microprofile-health/blob/master/spec/src/main/...] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 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 closed WFLY-14189. ---------------------------------------- Resolution: Done > 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: EJB, Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > 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 (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2068) Upgrade to MicroProfile JWT 1.2

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-2068: ------------------------------------- Summary: Upgrade to MicroProfile JWT 1.2 Key: ELY-2068 URL: https://issues.redhat.com/browse/ELY-2068 Project: WildFly Elytron Issue Type: Component Upgrade Components: MicroProfile Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.14.2.CR1 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14282) HostExcludesTestCase.testHostExcludes fails with wildfly-ee-galleon-pack server distribution

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-14282?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-14282: ---------------------------------------- Steps to Reproduce: $ cd wildfly/testsuite/domain $ mvn clean install \-Dtest=HostExcludesTestCase \-DtestLogToFile=false \-Dtestsuite.default.build.project.prefix=ee\- was: $ cd wildfly/testsuite/domain $ mvn clean install -Dtest=HostExcludesTestCase -DtestLogToFile=false -Dtestsuite.default.build.project.prefix=ee- > HostExcludesTestCase.testHostExcludes fails with wildfly-ee-galleon-pack server distribution > -------------------------------------------------------------------------------------------- > > Key: WFLY-14282 > URL: https://issues.redhat.com/browse/WFLY-14282 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Minor > > HostExcludesTestCase.testHostExcludes verifies the host exclusions configuration. When this test is executed on a server built by using the wildfly-ee-galleon-pack it fails with the following error: > {noformat} > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.202 s <<< FAILURE! - in org.jboss.as.test.integration.domain.HostExcludesTestCase > [ERROR] testHostExcludes(org.jboss.as.test.integration.domain.HostExcludesTestCase) Time elapsed: 1.039 s <<< FAILURE! > java.lang.AssertionError: These exclusions are not required for WildFly14.0 host-exclude: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.health-smallrye, org.wildfly.extension.microprofile.config-smallrye] > at org.junit.Assert.fail(Assert.java:89) > at org.jboss.as.test.integration.domain.HostExcludesTestCase.testHostExcludes(HostExcludesTestCase.java:375) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) > {noformat} > The error can be considered as just noise because it is not problematic to have unrequited exclusions. We have either fix the test to be less restrictive or clean the unneeded exclusions from the configuration since they are unrequired -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14282) HostExcludesTestCase.testHostExcludes fails with wildfly-ee-galleon-pack server distribution

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-14282: ------------------------------------------- Summary: HostExcludesTestCase.testHostExcludes fails with wildfly-ee-galleon-pack server distribution Key: WFLY-14282 URL: https://issues.redhat.com/browse/WFLY-14282 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana HostExcludesTestCase.testHostExcludes verifies the host exclusions configuration. When this test is executed on a server built by using the wildfly-ee-galleon-pack it fails with the following error: {noformat} [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.202 s <<< FAILURE! - in org.jboss.as.test.integration.domain.HostExcludesTestCase [ERROR] testHostExcludes(org.jboss.as.test.integration.domain.HostExcludesTestCase) Time elapsed: 1.039 s <<< FAILURE! java.lang.AssertionError: These exclusions are not required for WildFly14.0 host-exclude: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.health-smallrye, org.wildfly.extension.microprofile.config-smallrye] at org.junit.Assert.fail(Assert.java:89) at org.jboss.as.test.integration.domain.HostExcludesTestCase.testHostExcludes(HostExcludesTestCase.java:375) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) {noformat} The error can be considered as just noise because it is not problematic to have unrequited exclusions. We have either fix the test to be less restrictive or clean the unneeded exclusions from the configuration since they are unrequired -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5944) DMN OAS investigate InputData with undefined typeRef

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5944: -------------------------------------- Summary: DMN OAS investigate InputData with undefined typeRef Key: DROOLS-5944 URL: https://issues.redhat.com/browse/DROOLS-5944 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 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: ---------------------------------------------- I thought I could avoid the xml file since "other" was the default security domain, for other security features it's picked up correctly. Anyway, I will restore the file. Thank you > 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: EJB, Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > 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 (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14201) Integrate MP Config 2.0 into EAP

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14201?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFLY-14201: ----------------------------------- [~msvehla] Will you be the tester? This is 'done' from our side, as in merged to the feature branch > Integrate MP Config 2.0 into EAP > -------------------------------- > > Key: WFLY-14201 > URL: https://issues.redhat.com/browse/WFLY-14201 > Project: WildFly > Issue Type: Feature Request > Components: MP Config > Reporter: Stefano Maestri > Assignee: Kabir Khan > Priority: Major > Labels: MP4.0, merged-to-feature-branch > > See: > [Config 2.0|https://github.com/microprofile/microprofile-wg/issues/9] > [https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/...] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

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

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Diana Vilkolakova commented on WFLY-14189: ------------------------------------------ [~alessandromoscatelli] you can avoid adding the dependency by specifying security domain in jboss-web.xml instead. > 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: EJB, Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > 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 (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021