August 2015 - jboss-jira - Jboss List Archives

[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: 2.0.0.CR1 (was: 2.0.0.Alpha9) > 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: 2.0.0.CR1 > > > 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.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-25: ----------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Alpha9) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFCORE-25 > URL: https://issues.jboss.org/browse/WFCORE-25 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 2.0.0.CR1 > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-304) Enable user agent and address filters.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-304?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-304: ------------------------------------ Fix Version/s: (was: 2.0.0.Alpha9) Unscheduling as the parent task is not scheduled. > Enable user agent and address filters. > -------------------------------------- > > Key: WFCORE-304 > URL: https://issues.jboss.org/browse/WFCORE-304 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-296) Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-296?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-296: ------------------------------------ Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Alpha9) > Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https:// > --------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-296 > URL: https://issues.jboss.org/browse/WFCORE-296 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.CR1 > > > From [~dmlloyd] > {quote} > When we have multi-layer protocol going on, the URI scheme we should use > is like this: > outer+middle+inner:// > {quote} > Switch URI schemes from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https:// > The existing schemes will be needed for backwards compatibility but somehow deprecated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-266) Deprecate the ParameterValidator constructor variants that accept allowNull and allowExpressions params

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-266?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-266: ------------------------------------ Fix Version/s: 3.0.0.Beta1 (was: 2.0.0.Alpha9) > Deprecate the ParameterValidator constructor variants that accept allowNull and allowExpressions params > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-266 > URL: https://issues.jboss.org/browse/WFCORE-266 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Beta1 > > > Most of the ParameterValidator implementations that get passed to AttributeDefinition accept params to control whether null and expressions are allowed. These are now redundant, as AttributeDefinition wraps the provided validator with NillableOrExpressionParameterValidator, and it handles that aspect of validation based on the settings of the AD. > So we should deprecate these constructor variants to let people know they aren't needed. Ideally shift the code as well. > CRITICAL: before doing this, make sure the AttributeDefinition variants that support complex types properly wrap any validators that are configured for *element* validation. A quick look shows that ListAttributeDefinition.Builder and MapAttributeDefinition.Builder do. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-683) ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-683?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-683: ------------------------------------ Fix Version/s: 3.0.0.Alpha1 (was: 2.0.0.Alpha9) > ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-683 > URL: https://issues.jboss.org/browse/WFCORE-683 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.CR1 > Reporter: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > The two inner class OSHs in ModuleLoadingResourceDefinition don't deal with exceptions properly. They invoke AccessController.doPrivileged and then deal with any PrivilegedActionException by rethrowing as OperationFailedException. > OperationFailedException represents a client mistake and is handled as such (e.g. isn't logged in the server log.) It shouldn't be thrown here unless the PrivilegedActionException.getCause() value is itself an OFE. Otherwise, the OSHs should throw a RuntimeException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-646) Product to Project Schema and Model Sync

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-646?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-646: ------------------------------------ Fix Version/s: 2.0.0.CR1 (was: 2.0.0.Alpha9) > Product to Project Schema and Model Sync > ---------------------------------------- > > Key: WFCORE-646 > URL: https://issues.jboss.org/browse/WFCORE-646 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.CR1 > > > Periodic sync of EAP schemas with WildFly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-107: ------------------------------------ Fix Version/s: 3.0.0.Beta1 (was: 2.0.0.Alpha9) > Update whoami operation to return authentication mechanism where verbose=true > ----------------------------------------------------------------------------- > > Key: WFCORE-107 > URL: https://issues.jboss.org/browse/WFCORE-107 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta1 > > > The admin console currently contains a "logout" handler that follows a round of HTTP message exchanges to trick the web browser into forgetting the credentials it has cached. > This only makes sense where the browser has cached a credential - if we return the authentication mechanism then the console can make a better decision regarding displaying the logout link or could change the implementation so display a message to the user explaining why logout does not make sense. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

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: 2.0.0.CR1 (was: 2.0.0.Alpha9) [~dlofthouse] Please resolve or reschedule. > 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: 2.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 1 month

1
0
0 / 0

[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: 2.0.0.CR1 (was: 2.0.0.Alpha9) [~dlofthouse] Please resolve or reschedule. > 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: 2.0.0.CR1 > > > 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.15#6346)

10 years, 1 month

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 August 2015