June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2909) Upgrade WildFly Elytron to 1.1.0.Beta49

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2909?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2909: ------------------------------- Fix Version/s: 3.0.0.Beta25 (was: 3.0.0.Beta24) > Upgrade WildFly Elytron to 1.1.0.Beta49 > --------------------------------------- > > Key: WFCORE-2909 > URL: https://issues.jboss.org/browse/WFCORE-2909 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta25 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2349) Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2349?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-2349: ------------------------------- Fix Version/s: 3.0.0.Beta25 (was: 3.0.0.Beta24) > Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients. > --------------------------------------------------------------------------------- > > Key: WFCORE-2349 > URL: https://issues.jboss.org/browse/WFCORE-2349 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Fix For: 3.0.0.Beta25 > > > Other services such as EJB and transactions have a Remote*Permission to verify the remote client has the required permission to use that service - this should be repeated for the management related services to control what a remote client can and can not connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1606) Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi... ] Kabir Khan reopened WFCORE-1606: -------------------------------- > Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1606 > URL: https://issues.jboss.org/browse/WFCORE-1606 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.10.Final > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Beta25 > > > When security-realm, which is set as http-interface security-realm in management-interfaces, is modified and operation used {allow-resource-service-restart=true} header then server is NOT in reload-required state but modified security realm does not work correctly until server is manually reloaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8887) Cannot remove AUTH protocol referencing elytron capabilities

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8887?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-11341 to WFLY-8887: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8887 (was: JBEAP-11341) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: No Release (was: 7.1.0.DR19) > Cannot remove AUTH protocol referencing elytron capabilities > ------------------------------------------------------------ > > Key: WFLY-8887 > URL: https://issues.jboss.org/browse/WFLY-8887 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Introduced with JBEAP-11129, all three token types are affected: plain, digest, cipher. > First time the {{remove}} operation is attempted it results in > {noformat} > { > "outcome" => "failed", > "rolled-back" => true > } > {noformat} > and server logs this NPE: > {noformat} > 07:43:56,549 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0403: Unexpected failure during execution of the following operation(s): [{ > "address" => [ > ("subsystem" => "jgroups"), > ("stack" => "udp"), > ("protocol" => "AUTH") > ], > "operation" => "remove", > "operation-headers" => { > "caller-type" => "user", > "access-mechanism" => "NATIVE" > } > }]: java.lang.NullPointerException > at org.jboss.as.controller.AbstractOperationContext.getStepExecutionStatus(AbstractOperationContext.java:755) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:717) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:443) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1398) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} > The second time the operation is attempted, the result is still failure, but the cause is different: > {noformat} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {noformat} > {noformat} > 07:59:52,788 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("remove") failed - address: ([ > ("subsystem" => "jgroups"), > ("stack" => "udp"), > ("protocol" => "AUTH") > ]): java.lang.NullPointerException > at org.jboss.as.controller.AbstractRemoveStepHandler.performRemove(AbstractRemoveStepHandler.java:123) > at org.jboss.as.clustering.controller.RemoveStepHandler.performRemove(RemoveStepHandler.java:103) > at org.jboss.as.controller.AbstractRemoveStepHandler.execute(AbstractRemoveStepHandler.java:70) > at org.jboss.as.clustering.controller.RestartParentResourceRemoveStepHandler.execute(RestartParentResourceRemoveStepHandler.java:49) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:973) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:719) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:443) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1398) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2914) Upgrade to Undertow 1.4.16.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2914?page=com.atlassian.jira.plugi... ] Kabir Khan moved JBEAP-11340 to WFCORE-2914: -------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2914 (was: JBEAP-11340) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: (was: Web (Undertow)) > Upgrade to Undertow 1.4.16.Final > -------------------------------- > > Key: WFCORE-2914 > URL: https://issues.jboss.org/browse/WFCORE-2914 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Kabir Khan > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1597) Implement profile for integration with Signavio's DMN modeler

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1597?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1597: ---------------------------------- Description: Signavio implements a number of extensions to the DMN standard. As they are a Red Hat partner, we will need to implement a profile in the runtime engine that enables and supports those extensions. A short list of extensions is as follows. Details will be added to individual tickets: * Support additional FEEL functions and alternate names for existing functions * Support the Multi Instance Decision node * Support character '?' for interpolation of values in a DT cell * Support constraints on List inputs in DT cells * Support model composition through BKMs was: Signavio implement's a number of extensions to the DMN standard. As a Red Hat partner, we will need to implement a profile in the engine that enables and supports those extensions for runtime. A short list of extensions is as follows. Details will be added to individual tickets: * Support additional FEEL functions and alternate names for existing functions * Support the Multi Instance Decision node * Support character '?' for interpolation of values in a DT cell * Support constraints on List inputs in DT cells * Support model composition through BKMs > Implement profile for integration with Signavio's DMN modeler > ------------------------------------------------------------- > > Key: DROOLS-1597 > URL: https://issues.jboss.org/browse/DROOLS-1597 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > Signavio implements a number of extensions to the DMN standard. As they are a Red Hat partner, we will need to implement a profile in the runtime engine that enables and supports those extensions. > A short list of extensions is as follows. Details will be added to individual tickets: > * Support additional FEEL functions and alternate names for existing functions > * Support the Multi Instance Decision node > * Support character '?' for interpolation of values in a DT cell > * Support constraints on List inputs in DT cells > * Support model composition through BKMs -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1602) Support model composition through BKM invocation

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1602?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1602: ---------------------------------- Parent: DROOLS-1597 Issue Type: Sub-task (was: Feature Request) > Support model composition through BKM invocation > ------------------------------------------------ > > Key: DROOLS-1602 > URL: https://issues.jboss.org/browse/DROOLS-1602 > Project: Drools > Issue Type: Sub-task > Components: dmn engine > Affects Versions: 7.1.0.Beta2 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > Attachments: Screenshot 2017-06-02 19.56.31.png > > > Signavio supports model composition through BKM integration. In order to integrate with them, we will need to add this feature to the runtime. > See screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1602) Support model composition through BKM invocation

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1602: ------------------------------------- Summary: Support model composition through BKM invocation Key: DROOLS-1602 URL: https://issues.jboss.org/browse/DROOLS-1602 Project: Drools Issue Type: Feature Request Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Attachments: Screenshot 2017-06-02 19.56.31.png Signavio supports model composition through BKM integration. In order to integrate with them, we will need to add this feature to the runtime. See screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1601) Support constraints on List inputs in DT cells

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1601: ------------------------------------- Summary: Support constraints on List inputs in DT cells Key: DROOLS-1601 URL: https://issues.jboss.org/browse/DROOLS-1601 Project: Drools Issue Type: Sub-task Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Make sure the unary tests in the decision tables work fine with list inputs. This ticket might require no changes on our side, but we should at least add a couple tests to avoid regressions in the future. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1600) Support character ? for interpolation in values in a DT cell

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1600: ------------------------------------- Summary: Support character ? for interpolation in values in a DT cell Key: DROOLS-1600 URL: https://issues.jboss.org/browse/DROOLS-1600 Project: Drools Issue Type: Sub-task Components: dmn engine Affects Versions: 7.1.0.Beta2 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Attachments: Screenshot 2017-06-02 19.50.40.png Signavio uses the character ? to interpolate the expression value into decision table cells. E.g.: =(1 - Discount) * ? In the above example, '?' is replaced my the result of the decision table input expression. See attached screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 June 2017