December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2075) Upgrade to WildFly Elytron 1.1.0.Beta17

by Brian Stansberry (JIRA)

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

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2068) HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2068?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2068: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > HTTPSConnectionWithCLITestCase and HTTPSManagementInterfaceTestCase Failing Due To Native Protocol Issue > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2068 > URL: https://issues.jboss.org/browse/WFCORE-2068 > Project: WildFly Core > Issue Type: Bug > Components: Remoting, Test Suite > Reporter: Darran Lofthouse > Assignee: Jean-Francois Denise > Priority: Blocker > Fix For: 3.0.0.Alpha15 > > > The listed test case is failing during clean up with the following error: - > {noformat} > java.io.IOException: java.io.IOException: WFLYPRT0054: Channel closed > at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80) > {noformat} > The stage of the test using HTTP Upgrade over a HTTPS connection appears to be working fine, the issue is with the native management interface used for test clean up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2067) Upgrade to JBoss Remoting 5.0.0.Beta10

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2067?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2067: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > Upgrade to JBoss Remoting 5.0.0.Beta10 > -------------------------------------- > > Key: WFCORE-2067 > URL: https://issues.jboss.org/browse/WFCORE-2067 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha15 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2060) Support Elytron RoleMapper categories

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2060?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2060: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > Support Elytron RoleMapper categories > ------------------------------------- > > Key: WFCORE-2060 > URL: https://issues.jboss.org/browse/WFCORE-2060 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha15 > > > (Support for this could be added later, just scheduling in current releases for now if we have time) > The Elytron role mapping configuration can contain different mappers for different categories, this issue is to make use of categories for management role mapping. > We need to decide if we use hard coded names, some naming convention which is part hard coded, part based on deployment or a fully configurable category. > On the access=authorization resource this could simply be an optional String 'role-category' if we go for configured. Possibly a boolean to state if we fallback to the default RoleMapping on the domain. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2059) Deprecate management role mappings

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2059?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2059: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > Deprecate management role mappings > ---------------------------------- > > Key: WFCORE-2059 > URL: https://issues.jboss.org/browse/WFCORE-2059 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha15 > > > The Elytron SecurityDomain becomes the common point where policy information such as role mapping should be handled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7719) HotRod-based distributed session manager

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7719: ---------------------------------- Summary: HotRod-based distributed session manager Key: WFLY-7719 URL: https://issues.jboss.org/browse/WFLY-7719 Project: WildFly Issue Type: Feature Request Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7718) It is possible to set max-concurrent-requests attribute of request limit filter in undertow to value lower than one

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7718?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-7608 to WFLY-7718: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7718 (was: JBEAP-7608) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Undertow) (was: User Experience) Affects Version/s: (was: 7.1.0.DR9) > It is possible to set max-concurrent-requests attribute of request limit filter in undertow to value lower than one > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7718 > URL: https://issues.jboss.org/browse/WFLY-7718 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > According to https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io... it should not be possible to perform this operation: {{/subsystem=undertow/configuration=filter/request-limit=foo:add(max-concurrent-requests=-42)}} so it looks like no value check is performed in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2078) Update discovery to 1.0.0.Beta3

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFCORE-2078: -------------------------------------- Summary: Update discovery to 1.0.0.Beta3 Key: WFCORE-2078 URL: https://issues.jboss.org/browse/WFCORE-2078 Project: WildFly Core Issue Type: Component Upgrade Components: Server Affects Versions: 3.0.0.Alpha13 Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7300) OperationHandlers that register DeploymentProcessor should do it only on boot

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7300?page=com.atlassian.jira.plugin.... ] James Perkins reopened WFLY-7300: --------------------------------- There is one issue with the legacy batch subsystem. It is still using the {{performRuntime(OperationContext, ModelNode, ModelNode)}} which will not be executed from the {{AbstractBoottimeAddStepHandler}}. > OperationHandlers that register DeploymentProcessor should do it only on boot > ----------------------------------------------------------------------------- > > Key: WFLY-7300 > URL: https://issues.jboss.org/browse/WFLY-7300 > Project: WildFly > Issue Type: Bug > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 11.0.0.Alpha1 > > > Registering a DeploymentProcessor is a boot only operation. Thus instead of extends AbstractAddStepHandler they should extend AbstractBoottimeAddStepHandler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2035) Authorization Failures Starting After Enabling RBAC

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2035?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2035: ------------------------------------- Description: Enabling RBAC on WildFly is causing authorization failures on reload and it remains in unusable state afterwards. It is not possible to use neither CLI or Web Console thus it is not possible to configure or control server in any way. {noformat} 2016-11-22 14:43:27,256 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.txn.ArjunaTransactionManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: WFLYTX0006: Failed to configure object store browser bean at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:150) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) 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:745) Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:877) at com.arjuna.ats.arjuna.tools.osb.util.JMXServer.registerMBean(JMXServer.java:120) at com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser.start(ObjStoreBrowser.java:154) at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:148) ... 5 more {noformat} {noformat} 2016-11-22 14:43:27,396 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:73) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) 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:745) Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:877) at org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:343) at org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigImpl.java:70) at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:70) ... 5 more {noformat} {noformat} 2016-11-22 14:43:30,434 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache-container.web: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache-container.web: org.infinispan.commons.CacheException: Failure while registering mbeans at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:69) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) 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:745) Caused by: org.infinispan.commons.CacheException: Failure while registering mbeans at org.infinispan.jmx.ComponentsJmxRegistration.registerMBeans(ComponentsJmxRegistration.java:67) at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:38) at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:657) at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.lambda$build$3(CacheContainerBuilder.java:106) at org.wildfly.clustering.service.SuppliedValueService.lambda$new$0(SuppliedValueService.java:42) at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:67) ... 5 more Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) at org.jboss.as.jmx.PluggableMBeanServerImpl.isRegistered(PluggableMBeanServerImpl.java:784) at org.infinispan.jmx.JmxUtil.registerMBean(JmxUtil.java:66) at org.infinispan.jmx.ComponentsJmxRegistration.registerMBeans(ComponentsJmxRegistration.java:64) ... 11 more {noformat} was:Enabling RBAC and reload leads to a lot of exceptions in server log in both standalone and domain mode. See attached server log. > Authorization Failures Starting After Enabling RBAC > --------------------------------------------------- > > Key: WFCORE-2035 > URL: https://issues.jboss.org/browse/WFCORE-2035 > Project: WildFly Core > Issue Type: Bug > Components: JMX, Security > Reporter: Ingo Weiss > Assignee: Darran Lofthouse > Priority: Blocker > > Enabling RBAC on WildFly is causing authorization failures on reload and it remains in unusable state afterwards. It is not possible to use neither CLI or Web Console thus it is not possible to configure or control server in any way. > {noformat} > 2016-11-22 14:43:27,256 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.txn.ArjunaTransactionManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: WFLYTX0006: Failed to configure object store browser bean > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:150) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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:745) > Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) > at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:877) > at com.arjuna.ats.arjuna.tools.osb.util.JMXServer.registerMBean(JMXServer.java:120) > at com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser.start(ObjStoreBrowser.java:154) > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:148) > ... 5 more > {noformat} > {noformat} > 2016-11-22 14:43:27,396 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:73) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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:745) > Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) > at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:877) > at org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:343) > at org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigImpl.java:70) > at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:70) > ... 5 more > {noformat} > {noformat} > 2016-11-22 14:43:30,434 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache-container.web: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache-container.web: org.infinispan.commons.CacheException: Failure while registering mbeans > at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:69) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > 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:745) > Caused by: org.infinispan.commons.CacheException: Failure while registering mbeans > at org.infinispan.jmx.ComponentsJmxRegistration.registerMBeans(ComponentsJmxRegistration.java:67) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:38) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:657) > at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.lambda$build$3(CacheContainerBuilder.java:106) > at org.wildfly.clustering.service.SuppliedValueService.lambda$new$0(SuppliedValueService.java:42) > at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:67) > ... 5 more > Caused by: javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1211) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1197) > at org.jboss.as.jmx.PluggableMBeanServerImpl.isRegistered(PluggableMBeanServerImpl.java:784) > at org.infinispan.jmx.JmxUtil.registerMBean(JmxUtil.java:66) > at org.infinispan.jmx.ComponentsJmxRegistration.registerMBeans(ComponentsJmxRegistration.java:64) > ... 11 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 December 2016