October 2014 - jboss-jira - Jboss List Archives

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-103: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > 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.Alpha10 > > > 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.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-94) Add -secmgr to startup scripts and propagate -secmgr through the domain

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-94?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFCORE-94: --------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > Add -secmgr to startup scripts and propagate -secmgr through the domain > ----------------------------------------------------------------------- > > Key: WFCORE-94 > URL: https://issues.jboss.org/browse/WFCORE-94 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Scripts > Reporter: Kabir Khan > Assignee: James Perkins > Fix For: 1.0.0.Alpha10 > > > The preferred mechanism to enable a security manager is to use the -secmgr module option. Modify the scripts to make this easier to add, and make adjustments to propagate this through the domain. > The -secmgr module option is not visible from the launched process, so for the process controller and host controller to pass that on to the started host controller or server process respectively, a check is added to see if a security manager was enabeld. If a security manager is enabled, and -Djava.security.manager is not present in the system properties, we add the -secmgr module option when starting the next process. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-106) Enable GSSAPI/Kerberos Support for domain management over Remoting

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-106?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-106: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > Enable GSSAPI/Kerberos Support for domain management over Remoting > ------------------------------------------------------------------ > > Key: WFCORE-106 > URL: https://issues.jboss.org/browse/WFCORE-106 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha10 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-104) Add GSSAPI support to CLI

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-104?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-104: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > Add GSSAPI support to CLI > ------------------------- > > Key: WFCORE-104 > URL: https://issues.jboss.org/browse/WFCORE-104 > Project: WildFly Core > Issue Type: Sub-task > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Kerberos, management_security, > Fix For: 1.0.0.Alpha10 > > > Once the Native interface supports GSSAPI then the CLI will also need to support this. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-133) CLI -connect option throws full stacktrace exception

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-133?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-133: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > CLI -connect option throws full stacktrace exception > ---------------------------------------------------- > > Key: WFCORE-133 > URL: https://issues.jboss.org/browse/WFCORE-133 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha8 > Reporter: Joe Wertz > Assignee: Joe Wertz > Priority: Minor > Fix For: 1.0.0.Alpha10 > > > Full stacktrace is printed for exceptions that occur before the CLI connects to a server. > Instead, only the exception messages should be printed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-129: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha10 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

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

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-107: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.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: 1.0.0.Alpha10 > > > 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.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-146) Cleanup/fix IPV6 testsuite

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-146?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-146: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > Cleanup/fix IPV6 testsuite > -------------------------- > > Key: WFCORE-146 > URL: https://issues.jboss.org/browse/WFCORE-146 > Project: WildFly Core > Issue Type: Task > Affects Versions: 1.0.0.Alpha8 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 1.0.0.Alpha10 > > > CLI testsuite cannot be ported over to Core as we have problems with IPV6 testsuite. > Testsuite configuration for ipv6 should be unified and simplified to make all this work in core and in full without extra params to build -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-140) The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime()

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-140?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-140: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > The Resource for a deployment whose 'persistent' attribute is 'false' does not return 'true' from isRuntime() > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-140 > URL: https://issues.jboss.org/browse/WFCORE-140 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha8 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha10 > > > Scanner managed deployments have the deployment resource's 'persistent' attribute set to 'false'. This results in the StandaloneXml not persisting the resource to XML, but that depends on custom logic in StandaloneXml that reads the attribute. > The Resource for these deployments should return 'true' from isRuntime() so callers can decided about this without needing internal knowledge of the resource attributes. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-139) OperationContext should create runtime-only resources for addresses whose registration is runtime only

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-139?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-139: ---------------------------------- Fix Version/s: 1.0.0.Alpha10 (was: 1.0.0.Alpha9) > OperationContext should create runtime-only resources for addresses whose registration is runtime only > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-139 > URL: https://issues.jboss.org/browse/WFCORE-139 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha10 > > > The OperationContext.createResource method creates and adds a default Resource. The created Resource should return the same value from isRuntime() that the ManagementResourceRegistration associated with the target address returns from MRR.isRuntimeOnly() -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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