September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13220) A DeploymentException must be thrown if configured to use a PrivateKey

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13220?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13220: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > A DeploymentException must be thrown if configured to use a PrivateKey > ---------------------------------------------------------------------- > > Key: WFLY-13220 > URL: https://issues.redhat.com/browse/WFLY-13220 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Affects Versions: 19.0.0.Beta3 > Reporter: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > From section 9.2.0 of the Eclipse MicroProfile JWT specification, implementations are required to throw a DeploymentException when given a PrivateKey in any format. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13673) Some kind if layer test that verifies legacy security is not included.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13673?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13673: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Some kind if layer test that verifies legacy security is not included. > ---------------------------------------------------------------------- > > Key: WFLY-13673 > URL: https://issues.redhat.com/browse/WFLY-13673 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > I am currently looking at changes needed to prevent legacy security / PicketBox from being accidentally provisioned with Elytron security. > We should likely have a test that PicketBox is not present so if any future changes accidentally added a dependency this would be flagged quickly in CI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13706) Support a Galleon feature pack to install Keycloak adapters

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13706?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13706: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Support a Galleon feature pack to install Keycloak adapters > ----------------------------------------------------------- > > Key: WFLY-13706 > URL: https://issues.redhat.com/browse/WFLY-13706 > Project: WildFly > Issue Type: Feature Request > Components: Documentation, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > In conjunction with the bootable jar support currently being developed this feature request is to cover support for Keycloak client side adapter installation integrated with the Elytron security subsystem. > The main feature pack is anticipated to be delivered by the Keycloak project, however as this is specifically for use with WildFly we likely need WildFly documentation and possibly test cases so this Jira issue to to cover tasks required within WildFly. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13793: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Final > > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13679) Make legacy security optional for "org.wildfly.iiop-openjdk"

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13679?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13679: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Make legacy security optional for "org.wildfly.iiop-openjdk" > ------------------------------------------------------------ > > Key: WFLY-13679 > URL: https://issues.redhat.com/browse/WFLY-13679 > Project: WildFly > Issue Type: Sub-task > Components: IIOP, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > The dependency needs to optional so provisioning a layer with iiop-openjdk does not automatically pull in legacy security. > This is not just about making the module dependency optional, this is about understanding why it is not optional and identifying the steps required to make it optional. > This needs to consider: > * Default Configuration > * User Defined Configuration > Both of these can have different consequences depending on of they are used for: > * Resource defined services > * DeploymentUnitProcessor processing > iiop-openjdk module.xml: https://github.com/wildfly/wildfly/blob/master/ee-feature-pack/common/src... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13802) The undertow layer can not deploy deployments without the ee layer

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13802?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13802: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > The undertow layer can not deploy deployments without the ee layer > ------------------------------------------------------------------ > > Key: WFLY-13802 > URL: https://issues.redhat.com/browse/WFLY-13802 > Project: WildFly > Issue Type: Bug > Components: Build System, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > {code:java} > 16:35:06,234 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50) > at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:709) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:276) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13871: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Re-implement correct suspend/resume behaviour for EJB client > ------------------------------------------------------------ > > Key: WFLY-13871 > URL: https://issues.redhat.com/browse/WFLY-13871 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 21.0.0.Final > > > When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations. > This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored. > This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13883) Clustering TS: Enable Infinispan Server integration tests on Windows platform

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13883?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13883: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Clustering TS: Enable Infinispan Server integration tests on Windows platform > ----------------------------------------------------------------------------- > > Key: WFLY-13883 > URL: https://issues.redhat.com/browse/WFLY-13883 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 21.0.0.Final > > > Currently disabled due to ISPN-12041. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13855) remote-cache-container protocol-version allowed values contains last protocol version twice

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13855?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13855: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > remote-cache-container protocol-version allowed values contains last protocol version twice > ------------------------------------------------------------------------------------------- > > Key: WFLY-13855 > URL: https://issues.redhat.com/browse/WFLY-13855 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 21.0.0.Final > > > Clearly because of {{org.infinispan.client.hotrod.ProtocolVersion#PROTOCOL_VERSION_AUTO}} plus there is no pruning in place. > Fix is to use {{org.jboss.as.clustering.controller.validation.EnumValidator#EnumValidator(java.lang.Class<E>, java.util.EnumSet<E>)}} instead. > {code:json} > "protocol-version" => { > "type" => STRING, > "description" => "This property defines the protocol version that this client should use.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "3.0", > "allowed" => [ > "2.0", > "2.1", > "2.2", > "2.3", > "2.4", > "2.5", > "2.6", > "2.7", > "2.8", > "2.9", > "3.0", > "3.0" > ], > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13858) Bump the Undertow subsystem model version and schema to version 12

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13858?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13858: ------------------------------------ Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Bump the Undertow subsystem model version and schema to version 12 > ------------------------------------------------------------------ > > Key: WFLY-13858 > URL: https://issues.redhat.com/browse/WFLY-13858 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Affects Versions: 20.0.1.Final > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 21.0.0.Final > > > The Undertow subsystem schema should be bumped from 9 to 10 and the model version should be bumped from 9 to 10. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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