December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2043) Add System property to override timeout of testrunner.Server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2043?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2043: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > Add System property to override timeout of testrunner.Server > ------------------------------------------------------------ > > Key: WFCORE-2043 > URL: https://issues.jboss.org/browse/WFCORE-2043 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha15 > > > When debugging connectivity issues the 30s timeout can be a bit too short as attaching a debugger can pause the server or client so the timeout is hit and all processes are subsequently terminated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2031) Update description of security-realm in management interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2031?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2031: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > Update description of security-realm in management interfaces > ------------------------------------------------------------- > > Key: WFCORE-2031 > URL: https://issues.jboss.org/browse/WFCORE-2031 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > Fix For: 3.0.0.Alpha15 > > > Description of security-realm attribute in HTTP (and native) management interfaces says: > "The security realm to use for the HTTP management interface." or "The security realm to use for the native management interface." > However Elytron also uses security-realms. Description of mentioned about attribute should include information that it uses *legacy* security realm (not Elytron). Without word "legacy" it can be confusing since two different types of security-realm currently occur in configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2030) sasl-authentication-factory should be valid in combination with security-realm in native management interface in CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2030?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2030: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > sasl-authentication-factory should be valid in combination with security-realm in native management interface in CLI > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2030 > URL: https://issues.jboss.org/browse/WFCORE-2030 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Alpha15 > > > I am not able to add native management interface with both {{sasl-authentication-factory}} and {{security-realm}} attributes. According to comments in EAP7-545 Analysis document [1] setting both of them is valid configuration. However CLI consider this combination as invalid (when running server with standalone-elytron.xml): > {code} > /core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,security-realm=ApplicationRealm,socket-binding=management-http) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0105: sasl-authentication-factory is invalid in combination with security-realm", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2029) It is not possible to set Elytron for native management interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2029?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2029: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha14) > It is not possible to set Elytron for native management interface > ----------------------------------------------------------------- > > Key: WFCORE-2029 > URL: https://issues.jboss.org/browse/WFCORE-2029 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Alpha15 > > > I am not able to correctly configure native management interface to use Elytron. > I am adding some binding for native interface: > {code} > /socket-binding-group=standard-sockets/socket-binding=native:add(port=9999) > {code} > And then adding native management interface which uses Elytron sasl-authentication-factory ({{application-sasl-authentication}} is predefined in standalone-elytron.xml): > {code} > /core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,socket-binding=native) > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"] > }, > "rolled-back" => true > } > {code} > Following exception occurs in server log: > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "native-interface") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.sasl-authentication-factory"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.security.sasl-authentication-factory]"] > } > INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.security.sasl-authentication-factory (missing) dependents: [service jboss.remoting.server.management] > {code} > The same exception is thrown when I am trying to set SSL through Elytron {{ssl-context}} attribute in management native-interface. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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)

9 years, 1 month

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)

9 years, 1 month

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)

9 years, 1 month

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)

9 years, 1 month

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)

9 years, 1 month

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)

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 December 2016