August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5466) Intermittent Failure in org.jboss.as.test.integration.security.loginmodules.LdapExtLoginModuleTestCase

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5466: ------------------------------------- Summary: Intermittent Failure in org.jboss.as.test.integration.security.loginmodules.LdapExtLoginModuleTestCase Key: AS7-5466 URL: https://issues.jboss.org/browse/AS7-5466 Project: Application Server 7 Issue Type: Bug Components: Security, Test Suite Affects Versions: 7.1.2.Final (EAP) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[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

13 years, 5 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

13 years, 5 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

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] (AS7-5166) Remote/Local lookup with user authentication should work in the same way

by Fernando Rubbo (JIRA)

Fernando Rubbo created AS7-5166: ----------------------------------- Summary: Remote/Local lookup with user authentication should work in the same way Key: AS7-5166 URL: https://issues.jboss.org/browse/AS7-5166 Project: Application Server 7 Issue Type: Bug Components: EE, Security Affects Versions: 7.1.2.Final (EAP) Environment: Testing on windows Reporter: Fernando Rubbo Assignee: David Lloyd I'm opening this issue because nobody was able to answer my question in the discussions section. So, I strongly believe this is an issue of the JBoss 7. Let's to the issue: ctx.getCallerPrincipal() should work in the same way, no matter if it was a remote or a local lookup. For more details and an source code example, please see this thread: https://community.jboss.org/thread/202291 -- 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

13 years, 5 months

3
4
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

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] (AS7-5008) host-controller module does parse command line args too late

by Bernd Eckenfels (JIRA)

13 years, 5 months

2
8
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

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] (AS7-5445) deploy --name=(name with no extension) failed sometimes

by Cheng Fang (JIRA)

Cheng Fang created AS7-5445: ------------------------------- Summary: deploy --name=(name with no extension) failed sometimes Key: AS7-5445 URL: https://issues.jboss.org/browse/AS7-5445 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Cheng Fang Assignee: Brian Stansberry When deploying an app with --name option to specify a custom name, does the custom name have to include file extension to indicate its archive type? For example, is --name="nnn" valid, or does it have to be --name="nnn.war"? It seem requiring an archive type on a name is too restrictive. This is what I've observed: deploy --name="nnn" /tmp/hello.war deployed successfully, but there is no registration of web app context, so no way to run the webapp. Looks like the server haven't detected that it is a webapp from the name "nnn", and instead deployed it as a pojo module. With --name="nnn.war", everything works fine. deploy --name="nnn" /tmp/test-ejb.jar deployed successfully, and all the ejb's are registered. deploy --name="nnn" /tmp/test.ear deployed successfully, but ejb's inside the test.ear are not registered. deploy --name="nnn" /tmp/ejb-in-war.war failed, which could be the same cause as in the pure webapp deploy: {noformat} 21:47:14,391 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.deployment.unit.nnn.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.nnn.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "nnn" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader] at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:216) at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:86) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more Caused by: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:214) ... 7 more {noformat} -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (AS7-5444) runtime-name is used when logging undeploy

by Cheng Fang (JIRA)

Cheng Fang created AS7-5444: ------------------------------- Summary: runtime-name is used when logging undeploy Key: AS7-5444 URL: https://issues.jboss.org/browse/AS7-5444 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Affects Versions: 7.2.0.Alpha1 Reporter: Cheng Fang Assignee: David Bosschaert deploy a war and specify its runtime-name, and undeploy it: {noformat} deploy --runtime-name=nnn.war /Users/cfang/tmp/hello.war undeploy hello.war {noformat} In the server log it used the runtime-name to refer to the undeployed war, whereas I think the name (hello.war) should be used: {noformat} 17:31:08,290 INFO [org.jboss.as.server] (management-handler-thread - 55) JBAS018558: Undeployed "nnn.war" {noformat} -- 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

13 years, 5 months

2
6
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 August 2012