May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1228) Follow up on WFCORE-1202 and make the configuration available in the management model.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1228?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1228: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Follow up on WFCORE-1202 and make the configuration available in the management model. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1228 > URL: https://issues.jboss.org/browse/WFCORE-1228 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Alpha2 > > > WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model. > The system property should remain supported for backwards compatibility for those migrating from servers that relied on it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1190) Deprecate permgen attributes in the xsd

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1190?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1190: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Deprecate permgen attributes in the xsd > --------------------------------------- > > Key: WFCORE-1190 > URL: https://issues.jboss.org/browse/WFCORE-1190 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Alpha2 > > > Part of the parent task related to changing the xsd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1167) Upgrade jboss-invocation to include the new blockingCaller flag in InterceptorContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1167?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1167: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Upgrade jboss-invocation to include the new blockingCaller flag in InterceptorContext > ------------------------------------------------------------------------------------- > > Key: WFCORE-1167 > URL: https://issues.jboss.org/browse/WFCORE-1167 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Farah Juma > Assignee: David Lloyd > Labels: affects_elytron > Fix For: 3.0.0.Alpha2 > > > Upgrade jboss-invocation to a version that includes: > https://github.com/jbossas/jboss-invocation/commit/bae968117dffa6d179ca77... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1547) Integrate CredentialStore into Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1547?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1547: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Integrate CredentialStore into Core > ----------------------------------- > > Key: WFCORE-1547 > URL: https://issues.jboss.org/browse/WFCORE-1547 > Project: WildFly Core > Issue Type: Sub-task > Components: Security > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 3.0.0.Alpha2 > > > Create necessary API for integrating Elytron CredentialStore API into WildFly Core. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > 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 > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 3.0.0.Alpha2 > > > 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 (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1528) EAP 7 with secured management become unavailable after ~8 days

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1528?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1528: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > EAP 7 with secured management become unavailable after ~8 days > -------------------------------------------------------------- > > Key: WFCORE-1528 > URL: https://issues.jboss.org/browse/WFCORE-1528 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Environment: EAP 7.0.0.CR01 2-way ssl over remote https communication > Reporter: Simeon Pinder > Assignee: Brian Stansberry > Priority: Critical > Fix For: 2.2.0.CR2, 3.0.0.Alpha2 > > > Appears there may be an EAP 7.0.0.CR01 2-way ssl issue in domain mode. > Issue discovered by JON QE after testing for 8 days with SSL. > JON QE did not see the same issue when running identical test against EAP 6. > Restarting the remote client(JON Agent) did not repair/fix the issue, and only was repaired after EAP instance restarted. > See BZ https://bugzilla.redhat.com/show_bug.cgi?id=1330180#c0 for more details. > JON team would like some evaluation done to determine: > i)if this is EAP 7 issue or > ii)somehow just a JON issue > iii)suggestions on what to do when we try to reproduce properly or ways to shorten reproduce cycle. > This issue could affect GA release schedules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1515) Improve PersistentResourceDefinition to make it easier to register attribute write handlers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1515?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1515: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Improve PersistentResourceDefinition to make it easier to register attribute write handlers > ------------------------------------------------------------------------------------------- > > Key: WFCORE-1515 > URL: https://issues.jboss.org/browse/WFCORE-1515 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 3.0.0.Alpha2 > > > Currently if you want to take register custom write handler you need to override whole registerAttributes methods and do it yourself all the way. > We could add PersistentResourceDefinition.getAttributeHandlers() method that returns > a Map<String, OperationStepHandler>. > And then registerAttributes uses the map instead of hardcoding ReloadRequiredWriteAttributeHandler. Default impl just fills the map values with > ReloadRequiredWriteAttributeHandler. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1489) Expose (un)registerNotificationHandler() on OperationContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1489?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1489: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Expose (un)registerNotificationHandler() on OperationContext > ------------------------------------------------------------ > > Key: WFCORE-1489 > URL: https://issues.jboss.org/browse/WFCORE-1489 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha2 > > > Currently the only way to (un)register notifications is via the NotificationHandlerRegistration exposed by ModelController.getNotificationRegistry(). It would be nice to not have to install a service whose only purpose is to get hold of the ModelController from OSH's. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1438) Elytron integration with logging subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1438?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1438: ------------------------------------- Fix Version/s: 3.0.0.Alpha2 (was: 3.0.0.Alpha1) > Elytron integration with logging subsystem > ------------------------------------------ > > Key: WFCORE-1438 > URL: https://issues.jboss.org/browse/WFCORE-1438 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha2 > > > This is primarily an investigation task to start with, Logging can use syslog, Syslog access can be protected with TLS, Elytron is providing unified SSL configuration - do we need to bring these together. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5464) JDR report contains reference to AS7

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-5464?page=com.atlassian.jira.plugin.... ] Bartosz Spyrko-Śmietanko reassigned WFLY-5464: ---------------------------------------------- Assignee: Bartosz Spyrko-Śmietanko (was: Jesse Jaggars) > JDR report contains reference to AS7 > ------------------------------------ > > Key: WFLY-5464 > URL: https://issues.jboss.org/browse/WFLY-5464 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Bartosz Spyrko-Śmietanko > Priority: Minor > > *Description of problem:* > JDR report contains some legacy reference to AS7 > *How reproducible:* > Always > *Steps to Reproduce:* > # Create a JDR report using one of provided scripts (depends on OS) > # Check the created report > ## cd $JDR_LOCATION > ## find | grep as7 > *Actual results:* > {noformat} > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7 > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/tree.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/dump-services.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/deployment-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jarcheck.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/cluster-proxies-configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/local-module-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/system-properties.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jndi-view.json > {noformat} > *Expected results:* > No references to AS7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016