May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8842) Security checks when recursively reading resources

by Emanuel Muckenhuber (JIRA)

Security checks when recursively reading resources -------------------------------------------------- Key: JBAS-8842 URL: https://issues.jboss.org/browse/JBAS-8842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Emanuel Muckenhuber Assignee: Darran Lofthouse Currently the "read-resource" operation (GlobalOperationHandlers.ReadResourceHandler) just clones the subModel when recursively reading resources. We need to make sure that to also check the permissions for the children a node contains. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
7
0 / 0

[JBoss JIRA] (AS7-4701) One time password for management interfaces

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4701: ------------------------------------- Summary: One time password for management interfaces Key: AS7-4701 URL: https://issues.jboss.org/browse/AS7-4701 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 This task is to look into one time password use for the management consoles. This needs some further investigation as there is a trade off between ensuring a password is really one time and not valid for replays after use yet allowing a users web browser to keep establishing connections without forcing a new authentication every few minutes. The native interface also needs similar consideration however the native interface does allow for connections to be kept open for a long time more naturally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
2
0 / 0

[JBoss JIRA] (AS7-4039) Pushing configuration artifacts to domain servers

by Darragh Sherwin (JIRA)

Darragh Sherwin created AS7-4039: ------------------------------------ Summary: Pushing configuration artifacts to domain servers Key: AS7-4039 URL: https://issues.jboss.org/browse/AS7-4039 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Darragh Sherwin Assignee: Brian Stansberry It should be possible to push configurations artifacts like property files, keystores, etc to domain servers from a domain controller and for applications to reference these configuration artifacts in a generic manner. Weblogic provides this functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] (AS7-3568) Increase Test Coverage of Domain Management Security Options

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3568: ------------------------------------- Summary: Increase Test Coverage of Domain Management Security Options Key: AS7-3568 URL: https://issues.jboss.org/browse/AS7-3568 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.1.Final Presently there is plenty of testing relating to the default security options but now we need coverage of the non default options especially SSL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] (AS7-4514) Metrics/operations missing in platform mbean core-service

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4514: ------------------------------- Summary: Metrics/operations missing in platform mbean core-service Key: AS7-4514 URL: https://issues.jboss.org/browse/AS7-4514 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Heiko Rupp Assignee: Brian Stansberry The platform mbean(s) exposes more metrics that what is currently available at core-service=platform-mbean -Active Thread Count -Active Thread Group Count - JVM Free memory - JVM Total memory OS metrics - Free Physical Memory - Free Swap Memory - Process CPU Time - Committed Virtual Memory - open files Threading - SuspendedThreadCount - DeadLockedThreadCount Memory - operation to trigger gc And probably more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
7
0 / 0

[JBoss JIRA] (AS7-4412) Slave host does not register to DC when starting with --cached-dc and DC is available

by Manel Martinez (JIRA)

Manel Martinez created AS7-4412: ----------------------------------- Summary: Slave host does not register to DC when starting with --cached-dc and DC is available Key: AS7-4412 URL: https://issues.jboss.org/browse/AS7-4412 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Manel Martinez Assignee: Brian Stansberry Priority: Critical NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... ) When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-4400) Boolean validator

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-4400: ------------------------------------ Summary: Boolean validator Key: AS7-4400 URL: https://issues.jboss.org/browse/AS7-4400 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Jesper Pedersen Assignee: Brian Stansberry If you have a BOOLEAN in the DMR, but fail to type in the correct value, say "ture", it will get evaluated as false, while the user clearly meant true. We should have a strict validation against the "true" and "false" strings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-4271) Boot log writer ignores -Djboss.server.base.dir

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4271: ------------------------------- Summary: Boot log writer ignores -Djboss.server.base.dir Key: AS7-4271 URL: https://issues.jboss.org/browse/AS7-4271 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Heiko Rupp Assignee: Brian Stansberry When you start a server with -Djboss.server.base.dir this directory is used for configuration and also server.log, but not to populate the boot.log, which is still written to standalone/logs/boot.log. This is bad, as it will overwrite a boot.log for a server configuration that is running in parallel without -Djboss.server.base.dir= flag. Actually the logging config also seems to point at the old place hrupp 78046 0,0 1,1 1537296 96228 s005 S+ 10:55am 0:03.70 /usr/bin/java -D[Standalone] -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/devel/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/devel/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -jar /devel/jboss-as-7.1.1.Final/jboss-modules.jar -mp /devel/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/devel/jboss-as-7.1.1.Final -Djboss.server.base.dir=/devel/jboss-as-7.1.1.Final/standalone2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] (AS7-2626) Trailing forgotten --> does not generate a good error message on host.xml

by Jim Tyrrell (Created) (JIRA)

Trailing forgotten --> does not generate a good error message on host.xml ------------------------------------------------------------------------- Key: AS7-2626 URL: https://issues.jboss.org/browse/AS7-2626 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line... <domain-controller>   </domain-controller> Generates this error message: [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration Several lines further down...you get this message... [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). [Host Controller] at [row,col {unknown-source}]: [44,4] It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line. Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4. More verbosity would be nice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1103) Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase

by James Perkins (JIRA)

Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase -------------------------------------------------------------------------------------- Key: AS7-1103 URL: https://issues.jboss.org/browse/AS7-1103 Project: Application Server 7 Issue Type: Bug Reporter: James Perkins Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Below is the message from the error. ------------------------------------------------------------------------------- Test set: org.jboss.as.controller.CompositeOperationHandlerUnitTestCase ------------------------------------------------------------------------------- Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.625 sec <<< FAILURE! testRestartRequired(org.jboss.as.controller.CompositeOperationHandlerUnitTestCase) Time elapsed: 0.031 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[restart-requir]ed> but was:<[undefin]ed> at org.junit.Assert.assertEquals(Assert.java:123) at org.junit.Assert.assertEquals(Assert.java:145) at org.jboss.as.controller.CompositeOperationHandlerUnitTestCase.testRestartRequired(CompositeOperationHandlerUnitTestCase.java:496) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

7
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2012