January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-103) Add Full Kerberos Support

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-103: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > Add Full Kerberos Support > ------------------------- > > Key: WFCORE-103 > URL: https://issues.jboss.org/browse/WFCORE-103 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 1.0.0.Alpha17 > > > There are a number of steps required to full add Kerberos support - this is a top level tracking task to be resolved once all steps are complete. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-80) Upgrade org.apache.httpcomponents:httpclient to 4.3.2

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-80?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-80: ----------------------------------- Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > Upgrade org.apache.httpcomponents:httpclient to 4.3.2 > ----------------------------------------------------- > > Key: WFCORE-80 > URL: https://issues.jboss.org/browse/WFCORE-80 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Affects Versions: 1.0.0.Alpha5 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 1.0.0.Alpha17 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-489) The "access-mechanism" field in the active-operation resources is always undefined

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-489?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-489: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > The "access-mechanism" field in the active-operation resources is always undefined > ---------------------------------------------------------------------------------- > > Key: WFCORE-489 > URL: https://issues.jboss.org/browse/WFCORE-489 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 1.0.0.Alpha17 > > > The "access-mechanism" field in core-service=management/service=active-operations/active-operation=* is always undefined. The code that sets it is using the wrong var: > {code} > ModelNode accessMechanismNode = model.get(ACCESS_MECHANISM); > if (accessMechanism != null) { > accessMechanismNode.set(accessMechanismNode.toString()); > } > {code} > It should be accessMechanism.toString() -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-461) TestSuiteEnvironment should use privileged access to properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-461?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-461: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > TestSuiteEnvironment should use privileged access to properties > --------------------------------------------------------------- > > Key: WFCORE-461 > URL: https://issues.jboss.org/browse/WFCORE-461 > Project: WildFly Core > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha17 > > > The current TestSuiteEnvironment uses lots of {{System.getProperty()}} which fail under a security manager. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-279) Upgrade to JBoss Remoting after 4.0.5.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-279?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-279: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > Upgrade to JBoss Remoting after 4.0.5.Final > ------------------------------------------- > > Key: WFCORE-279 > URL: https://issues.jboss.org/browse/WFCORE-279 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha17 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-278) Revisit error message for an authentication failure.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-278?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-278: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > Revisit error message for an authentication failure. > ---------------------------------------------------- > > Key: WFCORE-278 > URL: https://issues.jboss.org/browse/WFCORE-278 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha17 > > > After authentication fails in the CLI the following error message is output: - > {code} > Unable to authenticate against controller at localhost:9990: Authentication failed: the server presented no authentication mechanisms > {code} > This text is a bit misleading, what it actually means is all mechanisms presented have either been excluded or attempted and now no further mechanisms are available to try. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-240) We need something similar to StandardConfigsXMLValidationUnitTestCase in Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-240?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-240: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > We need something similar to StandardConfigsXMLValidationUnitTestCase in Core > ----------------------------------------------------------------------------- > > Key: WFCORE-240 > URL: https://issues.jboss.org/browse/WFCORE-240 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Fix For: 1.0.0.Alpha17 > > > One feature of this test is that it validates that schemas are correct according to the schema schema, presently we only find out about errors in schemas when the wildfly testsuite is executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-137: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha17 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-496: ------------------------------------ Fix Version/s: 1.0.0.Alpha17 (was: 1.0.0.Alpha16) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha17 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-522) BlockingNotificationMBeanServer will NPE if resolvedDomain or expressionsDomain are not configured

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-522: --------------------------------------- Summary: BlockingNotificationMBeanServer will NPE if resolvedDomain or expressionsDomain are not configured Key: WFCORE-522 URL: https://issues.jboss.org/browse/WFCORE-522 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha16 Reporter: Brian Stansberry Assignee: Brian Stansberry If the jmx subsystem <expose-resolved-model/> and/or <expose-expression-model/> settings are not configured, but <remoting-connector/> is BlockingNotificationMBeanServer will throw NPEs in isInExposedModelControllerDomains due to passing null into java.util.regex.Pattern.matcher(...). Simply null checks will fix the problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 January 2015