October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2688) RestartParentWriteAttributeHandler.isResourceServiceRestartAllowed should check the AttributeDefinition

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2688?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2688: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > RestartParentWriteAttributeHandler.isResourceServiceRestartAllowed should check the AttributeDefinition > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2688 > URL: https://issues.jboss.org/browse/WFCORE-2688 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha2 > > > Besides checking with the context as to whether the allow-resource-service-restart header is set, if there is an AD available, it should be checked. > At one stroke this will turn off this ability for everything that doesn't specifically allow it. > Needs checks though to fix attributes that are meant to allow this but don't say so. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2687) Expose the current step operation's name and parameters via the OperationContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2687?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2687: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Expose the current step operation's name and parameters via the OperationContext > -------------------------------------------------------------------------------- > > Key: WFCORE-2687 > URL: https://issues.jboss.org/browse/WFCORE-2687 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha2 > > > Remove the need to pass the 'operation' ModelNode to a method for it to be able to learn about the currently effective operation. > OperationContext already exposes getCurrentAddress(). Add getCurrentOperationName() and getCurrentOperationParameter(String name). > The latter returns null if !operation.has(name) otherwise it returns whatever the node was. Or perhaps return undefined with an overloaded variant with a boolean param that lets the caller turn on getting null. > The getCurrentOperationParameter should reject 'name', 'address', 'operation-headers' etc as legal param names; only expose true parameters. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2589) Eliminate MSC OPTIONAL dependencies usage

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2589?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2589: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Eliminate MSC OPTIONAL dependencies usage > ----------------------------------------- > > Key: WFCORE-2589 > URL: https://issues.jboss.org/browse/WFCORE-2589 > Project: WildFly Core > Issue Type: Task > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 4.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2497) Convert *-authentication-factory resources to be child resources of security-domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2497?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2497: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Convert *-authentication-factory resources to be child resources of security-domain > ----------------------------------------------------------------------------------- > > Key: WFCORE-2497 > URL: https://issues.jboss.org/browse/WFCORE-2497 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha2 > > > This is a good example of where child resources work. > The authentication factory resources have a mandatory dependency on a single security domain. > The configuration within the factory is related to it's security domain. > There is only a single resource that can provide security domains. > The behaviour of the parent is unaffected by the existence or configuration of the child. > The parent and child manage their own services independently with the child's service depending on the parent's service. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2496: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Functionality in WildFly to encrypt database passwords > ------------------------------------------------------ > > Key: WFCORE-2496 > URL: https://issues.jboss.org/browse/WFCORE-2496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Carlton Zachary > Fix For: 4.0.0.Alpha2 > > > Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml. > Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

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.Alpha2 (was: 4.0.0.Alpha1) > 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.Alpha2 > > > 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, 6 months

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.Alpha2 (was: 4.0.0.Alpha1) > 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.Alpha2 > > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3073) Handle TERM gracefully

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3073?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3073: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Handle TERM gracefully > ---------------------- > > Key: WFCORE-3073 > URL: https://issues.jboss.org/browse/WFCORE-3073 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Ben Parees > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha2 > > > The wildfly server currently terminates immediately in response to a TERM signal. To achieve a clean shutdown requires invoking the CLI tooling. This is particularly problematic in container environments like kubernetes where the container process (wildfly in this case) is going to get a TERM signal when the container needs to be moved. > While it's possible to wrapper the process and handle the TERM and then invoke the CLI, it would be preferable for the server process itself to cleanly handle a TERM signal by waiting for in-flight requests to complete (w/ some grace period of course). > Having this as configurable behavior would be good if there are backwards compatibility concerns about introducing this behavior change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3019) The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3019?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3019: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > The bin/product.conf and the org.jboss.as.product:wildfly-core module should come in via an FP > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-3019 > URL: https://issues.jboss.org/browse/WFCORE-3019 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Fix For: 4.0.0.Alpha2 > > > For WFLY-4692 we moved the "product" stuff out of core-feature-pack and into dist. But this means it doesn't end up in the skinny dist produced by the "build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in dist/src/distribution should be its own FP. That one *perhaps* depends on core-feature-pack. Then build and dist use the new FP in addition to or instead of core-feature-pack. > So, core-feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on core-feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2857) Usage of wildfly.sasl.local-user.default-user in core configuration files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2857?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2857: ------------------------------------- Fix Version/s: 4.0.0.Alpha2 (was: 4.0.0.Alpha1) > Usage of wildfly.sasl.local-user.default-user in core configuration files > ------------------------------------------------------------------------- > > Key: WFCORE-2857 > URL: https://issues.jboss.org/browse/WFCORE-2857 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 4.0.0.Alpha2 > > > The property wildfly.sasl.local-user.default-user is present in some, commented out on other, and absent from some default configuation files in core. (the default host-slave.xml for example has it, but it appears to have no effect if removed). There is uneven usage of it throughout the testsuite config files. > We should review and make the usage (or non-usage) consistent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 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 October 2017