December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3181) Review CustomCredentialSecurityFactoryTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3181?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3181: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Review CustomCredentialSecurityFactoryTestCase > ---------------------------------------------- > > Key: WFCORE-3181 > URL: https://issues.jboss.org/browse/WFCORE-3181 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha5 > > > The test case CustomCredentialSecurityFactoryTestCase appears to be testing that the 'code does what it does' rather than testing the 'code is doing what it should'. > The test is testing a custom credential security factory can be called but the test is using HTTP Basic authentication and relying on SPNEGO authentication being triggered as this is the only mechanism that currently uses this factory. > Should a minor change be required to the SPNEGO authentication mechanism which affects when this credential factory is called this test case could subsequently fail. > If possible it would be better to convert this test to be a SPNEGO test and then test the behaviour of the credential security factory affects the mechanism as expected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3167) option to filter out aged out patches from the patching history

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3167?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3167: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > option to filter out aged out patches from the patching history > --------------------------------------------------------------- > > Key: WFCORE-3167 > URL: https://issues.jboss.org/browse/WFCORE-3167 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Patching > Affects Versions: 3.0.0.Beta30 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 4.0.0.Alpha5 > > > show-history management operation (and patch history cli command) returns all the patches that have been applied to the installation even if some of them have been aged out by executing ageout-history management operation. > In some cases it would be useful to filter out the aged out patches from the result, leaving only the patches that can actually be rolled back by a user. > That could be achieved by adding an optional boolean parameter exclude-agedout (with default value false to preserve the current behavior) to show-history operation. > The high level CLI command patch history could include an equivalent --exclude-agedout argument. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3107) Allow slave hosts to ignore missing RBAC config resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3107?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3107: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Allow slave hosts to ignore missing RBAC config resources > --------------------------------------------------------- > > Key: WFCORE-3107 > URL: https://issues.jboss.org/browse/WFCORE-3107 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha5 > > > Part of parent issue whereby slaves can ignore missing RBAC constraint resources for write requests coming from the DC. > If the DC sent the request, then the address is ok overall. So if it's missing on the slave that means the slave doesn't have that constraint registered and doesn't need to handle the op. > This fix could possibly be backported to the 2.1.x and to EAP 6.4.x in lieu of adding transformers as part of the parent issue. In the case of 2.1.x it also allows slaves to ignore the related extension even if the code for it is present (which is only a minor benefit.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3424) Replace MSC listeners with stability monitors

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3424?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3424: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Replace MSC listeners with stability monitors > --------------------------------------------- > > Key: WFCORE-3424 > URL: https://issues.jboss.org/browse/WFCORE-3424 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 4.0.0.Alpha2 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 4.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3397) Integrate improved thread pool implementation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3397?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3397: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Integrate improved thread pool implementation > --------------------------------------------- > > Key: WFCORE-3397 > URL: https://issues.jboss.org/browse/WFCORE-3397 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management, IO, Server, Test Suite > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 4.0.0.Alpha5 > > > Introduce new thread pool implementation with separate core/max size and configurable parameters, and reuse-idle-thread behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3386) Add configuration required to support JASPIC to the Elytron subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3386?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3386: ------------------------------------- Fix Version/s: 4.0.0.Alpha5 (was: 4.0.0.Alpha4) > Add configuration required to support JASPIC to the Elytron subsystem > --------------------------------------------------------------------- > > Key: WFCORE-3386 > URL: https://issues.jboss.org/browse/WFCORE-3386 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2953) Add a socket-handler resource to the logging subsystem

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2953?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-2953 at 11/30/17 7:08 PM: ----------------------------------------------------------------- Analysis Document: https://developer.jboss.org/docs/DOC-56154 was (Author: jamezp): Analysis Document: https://developer.jboss.org/docs/DOC-56153 > Add a socket-handler resource to the logging subsystem > ------------------------------------------------------ > > Key: WFCORE-2953 > URL: https://issues.jboss.org/browse/WFCORE-2953 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 4.0.0.Beta1 > > > The logging subsystem should include a resource for a {{socket-handler}}. This will be useful for structured formatters, such as the [{{json-formatter}}|WFCORE-2951]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2951) Add JSON formatter resources to the logging subsystem

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2951?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-2951: --------------------------------------- Analysis Document: https://developer.jboss.org/docs/DOC-56153 > Add JSON formatter resources to the logging subsystem > ----------------------------------------------------- > > Key: WFCORE-2951 > URL: https://issues.jboss.org/browse/WFCORE-2951 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 4.0.0.Beta1 > > > The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2952) Add an XML formatter resources to the logging subsystem

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2952?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-2952: --------------------------------------- Analysis Document: https://developer.jboss.org/docs/DOC-56153 > Add an XML formatter resources to the logging subsystem > ------------------------------------------------------- > > Key: WFCORE-2952 > URL: https://issues.jboss.org/browse/WFCORE-2952 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 4.0.0.Beta1 > > > The logging subsystem should include a resource for a {{xml-formatter}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017