February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1533) Integrate Management Access Control permission assignment with Elytron

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1533?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1533: ------------------------------------- Fix Version/s: (was: 4.0.0.CR1) > Integrate Management Access Control permission assignment with Elytron > ---------------------------------------------------------------------- > > Key: WFCORE-1533 > URL: https://issues.jboss.org/browse/WFCORE-1533 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Darran Lofthouse > Labels: affects_elytron > > A big portion of management role based access control is taking the assigned roles and then mapping these to the permissions for that role. > Elytron provides a new PermissionMapper interface that takes a SecurityIdentity and the roles mapped for that identity and returns a PermissionVerifier which can be as simple as a wrapper around a PermissionCollection. > This will also be a good opportunity to start to move the role mapping out of the core management model to Elytron. > After that Elytron allows for custom PermissionMapper implementations to be provided and associated with the domain using capabilities and requirements so we arrive at a point where provided the permission checks performed by management are generic enough custom PermissionMapper / PermissionVerifier implementations can be added that may or may not be role based. > _Note: As with everything we are doing old and new need to be supported in parallel for a while although this may be achieved by providing default Elytron implementations that are wrappers around the old._ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3411) CLI operation completion issues

by Marek Marusic (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3411?page=com.atlassian.jira.plugi... ] Marek Marusic reassigned WFCORE-3411: ------------------------------------- Assignee: Marek Marusic (was: Jean-Francois Denise) > CLI operation completion issues > ------------------------------- > > Key: WFCORE-3411 > URL: https://issues.jboss.org/browse/WFCORE-3411 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Marek Marusic > > :read-resource(proxies=<TAB> ==> :read-resource(proxies=alse should be :read-resource(proxies=false > :reload-servers(start-mode=normal,!blocking ==> gives nothing, should be :reload-servers(start-mode=normal,!blocking) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3568) Allow CLI output scrolling

by Marek Marusic (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3568?page=com.atlassian.jira.plugi... ] Marek Marusic reassigned WFCORE-3568: ------------------------------------- Assignee: Marek Marusic (was: Jean-Francois Denise) > Allow CLI output scrolling > -------------------------- > > Key: WFCORE-3568 > URL: https://issues.jboss.org/browse/WFCORE-3568 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 4.0.0.Alpha8 > Reporter: Chao Wang > Assignee: Marek Marusic > > Mouse scrolling is forbidden to large CLI out. User has to press {{Down}} or {{Enter}} to navigate. > It would be nice to allow fast scrolling or {{PgUp}} / {{PgDn}}. e.g. > {noformat} > [standalone@localhost:9990 /] /core-service=capability-registry:read-resource > { > "outcome" => "success", > "result" => { > "capabilities" => [ > { > "name" => "org.wildfly.batch.configuration", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=batch-jberet"] > }, > { > "name" => "org.wildfly.batch.job.repository.in-memory", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=batch-jberet/in-memory-job-repository=in-memory"] > }, > { > "name" => "org.wildfly.batch.thread.pool.batch", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=batch-jberet/thread-pool=batch"] > }, > { > "name" => "org.wildfly.clustering.cache.default-group.ejb", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=infinispan/cache-container=ejb"] > }, > { > "name" => "org.wildfly.clustering.cache.default-group.server", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=infinispan/cache-container=server"] > }, > { > "name" => "org.wildfly.clustering.cache.default-group.web", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=infinispan/cache-container=web"] > }, > { > "name" => "org.wildfly.clustering.cache.default-node-factory.ejb", > "dynamic" => false, > "scope" => "global", > "registration-points" => ["/subsystem=infinispan/cache-container=ejb"] > }, > { > "name" => "org.wildfly.clustering.cache.default-node-factory.server", > "dynamic" => false, > --More(2%)-- > {noformat} > Also, after pressing {{Down}} or {{Enter}} to display more output, user can not press {{up}} to go up. User has to inconveniently use scroll up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3646) WildFly Core test runner Server reload should wait before checking process state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3646?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3646: ------------------------------------- Issue Type: Enhancement (was: Bug) Priority: Minor (was: Major) > WildFly Core test runner Server reload should wait before checking process state > -------------------------------------------------------------------------------- > > Key: WFCORE-3646 > URL: https://issues.jboss.org/browse/WFCORE-3646 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 4.0.0.Beta2 > > > As reload is currently racy this should improve the reliability of the test suite -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3646) WildFly Core test runner Server reload should wait before checking process state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3646?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3646: ------------------------------------- Reporter: Brian Stansberry (was: Stuart Douglas) > WildFly Core test runner Server reload should wait before checking process state > -------------------------------------------------------------------------------- > > Key: WFCORE-3646 > URL: https://issues.jboss.org/browse/WFCORE-3646 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Stuart Douglas > Fix For: 4.0.0.Beta2 > > > As reload is currently racy this should improve the reliability of the test suite -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3646) WildFly Core test runner Server reload should wait before checking process state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3646?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3646: ------------------------------------- Reporter: Brian Stansberry (was: Brian Stansberry) > WildFly Core test runner Server reload should wait before checking process state > -------------------------------------------------------------------------------- > > Key: WFCORE-3646 > URL: https://issues.jboss.org/browse/WFCORE-3646 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Stuart Douglas > Fix For: 4.0.0.Beta2 > > > As reload is currently racy this should improve the reliability of the test suite -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3646) WildFly Core test runner Server reload should wait before checking process state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3646?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3646: ---------------------------------------- Assignee: Brian Stansberry (was: Stuart Douglas) > WildFly Core test runner Server reload should wait before checking process state > -------------------------------------------------------------------------------- > > Key: WFCORE-3646 > URL: https://issues.jboss.org/browse/WFCORE-3646 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Beta2 > > > As reload is currently racy this should improve the reliability of the test suite -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3646) WildFly Core test runner Server reload should wait before checking process state

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3646: ---------------------------------------- Summary: WildFly Core test runner Server reload should wait before checking process state Key: WFCORE-3646 URL: https://issues.jboss.org/browse/WFCORE-3646 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 4.0.0.Beta2 As reload is currently racy this should improve the reliability of the test suite -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2349?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2349: ------------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta2) > 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: 4.0.0.CR1 > > > 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.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2235) Intermittent module loading failure in InterdependentDeploymentTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2235?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2235: ------------------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta2) > Intermittent module loading failure in InterdependentDeploymentTestCase > ----------------------------------------------------------------------- > > Key: WFCORE-2235 > URL: https://issues.jboss.org/browse/WFCORE-2235 > Project: WildFly Core > Issue Type: Bug > Components: Modules, Server > Affects Versions: 4.0.0.Alpha6 > Reporter: Brian Stansberry > Assignee: Richard Opalka > Fix For: 4.0.0.CR1 > > Attachments: WFCORE-2235svcdump.txt > > > InterdependentDeploymentTestCase tests deployment handling of a set of interdependent deployments, where some of the dependencies are optional. > The test intermittently fails due to a ModuleLoadException while deploying one of the modules: > https://ci.wildfly.org/viewLog.html?buildId=42957&buildTypeId=WildFlyCore... > The most notable bit of info in the log is: > {code} > 17:32:08,639 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.module.service."deployment.interrelated-c.jar".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.interrelated-c.jar".main: WFLYSRV0179: Failed to load module: deployment.interrelated-c.jar > at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at org.jboss.msc.service.MSCExecutor$1.run(MSCExecutor.java:77) > 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.jboss.modules.ModuleNotFoundException: deployment.interrelated-c.jar > at org.jboss.modules.ModuleLoader$FutureModule.getModule(ModuleLoader.java:834) > at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:472) > at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:457) > at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:370) > at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:147) > at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:387) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:282) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:270) > at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68) > ... 6 more > {code} > The interrelated-c.jar deployment depends (*not optionally*) on interrelated-a.jar.The failure occurs during execution of a management op that redeploys interrelated-a.jar. FWIW, another deployment in the set, interrelated-f.jar, does depend optionally on interrelated-c.jar. > The full stdout output for the failed test in the above linked CI run also includes a dump of all MSC services following the failure. Note though that the failure does not result in MSC not obtaining stability. Inability to reach stability was the initial problem that led to the introduction of this test (see https://github.com/wildfly/wildfly-core/pull/2099.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018