December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2095) Add AuthenticationContext references to RemoteOutboundConnectionResourceDefinition

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2095?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2095: ------------------------------------- Fix Version/s: 3.0.0.Alpha16 (was: 3.0.0.Alpha15) > Add AuthenticationContext references to RemoteOutboundConnectionResourceDefinition > ---------------------------------------------------------------------------------- > > Key: WFCORE-2095 > URL: https://issues.jboss.org/browse/WFCORE-2095 > Project: WildFly Core > Issue Type: Feature Request > Components: Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha16 > > > The authentication-context reference will be to obtain an AuthenticationContext for the outbound connection. > The following attributes should be deprecated and made mutually exclusive with the new authentication-context-attribute: - > * username > * security-realm > * protocol -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

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

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.Alpha16 (was: 3.0.0.Alpha15) > Upgrade to JBoss Remoting 5.0.0.Beta11 > -------------------------------------- > > 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.Alpha16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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.Alpha16 (was: 3.0.0.Alpha15) > 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.Alpha16 > > > 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, 5 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.Alpha16 (was: 3.0.0.Alpha15) > 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.Alpha16 > > > (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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2058) Add a DomainXml_5 Parser

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2058?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2058: ------------------------------------- Fix Version/s: 3.0.0.Alpha16 (was: 3.0.0.Alpha15) > Add a DomainXml_5 Parser > ------------------------ > > Key: WFCORE-2058 > URL: https://issues.jboss.org/browse/WFCORE-2058 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[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.Alpha16 (was: 3.0.0.Alpha15) > 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.Alpha16 > > > 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, 5 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.Alpha16 (was: 3.0.0.Alpha15) > 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.Alpha16 > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2098) Upgrade to Elytron Web 1.0.0.Beta6

by Brian Stansberry (JIRA)

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

9 years, 5 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

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

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-828) Make PeerIdentityContext#setPeerIdentity protected

by Farah Juma (JIRA)

Farah Juma created ELY-828: ------------------------------ Summary: Make PeerIdentityContext#setPeerIdentity protected Key: ELY-828 URL: https://issues.jboss.org/browse/ELY-828 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Farah Juma Assignee: Farah Juma This will allow subclasses of PeerIdentityContext to be able to initialize the currently set peer identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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