June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-653) JBossPDP isDirectory called should check if the argument is of file pattern

by Anil Saldhana (JIRA)

Anil Saldhana created SECURITY-653: -------------------------------------- Summary: JBossPDP isDirectory called should check if the argument is of file pattern Key: SECURITY-653 URL: https://issues.jboss.org/browse/SECURITY-653 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: jbossxacml_2.0.6.Final Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: picketbox_xacml_2.0.7.Final https://issues.jboss.org/browse/JBPAPP-8462 has an exception for the AS7 environment. ====================== 15:51:51,112 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/pdp].[SOAPSAMLXACMLPDPServlet]] (http--127.0.0.1-8080-1) Allocate exception for servlet SOAPSAMLXACMLPDPServlet: java.lang.IllegalArgumentException: URI scheme is not "file" at java.io.File.<init>(File.java:366) [rt.jar:1.6.0_31] at org.jboss.security.xacml.core.JBossPDP.isDirectory(JBossPDP.java:590) [jbossxacml-2.0.6.Final.jar:2.0.6.Final] at org.jboss.security.xacml.core.JBossPDP.addPolicySets(JBossPDP.java:466) [jbossxacml-2.0.6.Final.jar:2.0.6.Final] at org.jboss.security.xacml.core.JBossPDP.bootstrap(JBossPDP.java:344) [jbossxacml-2.0.6.Final.jar:2.0.6.Final] at org.jboss.security.xacml.core.JBossPDP.<init>(JBossPDP.java:157) [jbossxacml-2.0.6.Final.jar:2.0.6.Final] at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.getPDP(SOAPSAMLXACMLPDP.java:126) [picketlink-fed-2.0.2.Final.jar:2.0.2.Final] at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.<init>(SOAPSAMLXACMLPDP.java:75) [picketlink-fed-2.0.2.Final.jar:2.0.2.Final] ========================== -- 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

11 years, 5 months

5
15
0 / 0

[JBoss JIRA] (AS7-4009) Domain Mode JMX access through the HostController

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4009: ------------------------------------- Summary: Domain Mode JMX access through the HostController Key: AS7-4009 URL: https://issues.jboss.org/browse/AS7-4009 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 This task is first to review if this should be considered. At the moment access to JMX is provided through the remoting connector of each AS instance - this task is to consider if we should actually make it available through the host controller with the host controller acting as a proxy. The main motivation being to separate management and app traffic. -- 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

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (AS7-4742) Security Realm Plug-Ins to provide their own configuration parsers.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4742: ------------------------------------- Summary: Security Realm Plug-Ins to provide their own configuration parsers. Key: AS7-4742 URL: https://issues.jboss.org/browse/AS7-4742 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 Security realm plug-ins are currently configured with name / value pairs - to make plug-ins easier to use by those that did not implement them we should consider allowing a custom XML parser to allow new configuration elements to be defined. -- 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

11 years, 5 months

1
3
0 / 0

[JBoss JIRA] (AS7-3406) Authorization check for JMX

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3406: ------------------------------------- Summary: Authorization check for JMX Key: AS7-3406 URL: https://issues.jboss.org/browse/AS7-3406 Project: Application Server 7 Issue Type: Sub-task Components: JMX, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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

11 years, 5 months

1
4
0 / 0

[JBoss JIRA] (AS7-3407) Authorization check for JNDI

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3407: ------------------------------------- Summary: Authorization check for JNDI Key: AS7-3407 URL: https://issues.jboss.org/browse/AS7-3407 Project: Application Server 7 Issue Type: Sub-task Components: Naming, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- 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

11 years, 5 months

1
4
0 / 0

[JBoss JIRA] (AS7-3414) Symbolic links inside deployed ear/war are not followed by web server

by Ronen Angluster (JIRA)

Ronen Angluster created AS7-3414: ------------------------------------ Summary: Symbolic links inside deployed ear/war are not followed by web server Key: AS7-3414 URL: https://issues.jboss.org/browse/AS7-3414 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1, 7.1.0.Beta1 Environment: Fedora 16 Reporter: Ronen Angluster Assignee: Alessio Soldano when creating a symbolic link inside a deployed ear/war the symbolic link's target is not followed when accessing it from a web browser i.e. in jboss-as/standalone/deplyoment/somedomain.ear/files we created a symbolic link named "version.js" which points to /usr/share/something/version.js the target file (/usr/share/...) is accessible by all (chmod'd to 777) and is readable by the jboss-as user which runs the Jboss application server. when accessing http://domain:8080/something/files/version.js we get an 404 error, seems like the file is not found by the server. when placing the file instead of symbolic link, the file is accessible and all is well -- 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

11 years, 5 months

7
10
0 / 0

[JBoss JIRA] (AS7-4639) Allow modification of the data-source-class and xa-data-source-class attributes from the console

by Heiko Braun (JIRA)

Heiko Braun created AS7-4639: -------------------------------- Summary: Allow modification of the data-source-class and xa-data-source-class attributes from the console Key: AS7-4639 URL: https://issues.jboss.org/browse/AS7-4639 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.2.Final-redhat1 -- 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

11 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (AS7-1628) Custom JSF deployment does not work altogether with CDI

by George Gastaldi (JIRA)

Custom JSF deployment does not work altogether with CDI ------------------------------------------------------- Key: AS7-1628 URL: https://issues.jboss.org/browse/AS7-1628 Project: Application Server 7 Issue Type: Bug Reporter: George Gastaldi When using another JSF impl (with flag org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL set to true) and a beans.xml is on WEB-INF, the following error occurs: {code:java} 12:33:07,066 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA 12:33:07,341 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA 12:33:07,394 INFO [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting 12:33:08,212 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted. 12:33:08,220 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) 12:33:08,267 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted. 12:33:08,276 INFO [org.jboss.as.logging] Removing bootstrap log handlers 12:33:08,293 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) 12:33:08,306 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem. 12:33:08,418 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem 12:33:08,426 INFO [org.jboss.as.naming] (MSC service thread 1-5) Starting Naming Service 12:33:08,429 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem 12:33:08,449 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem 12:33:08,453 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.Beta2 12:33:08,469 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3 12:33:08,482 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.Beta3 12:33:08,724 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-1) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\jdk6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:/powerlogic/jcompany55/java/bin/../jre/bin/server;D:/powerlogic/jcompany55/java/bin/../jre/bin;D:/powerlogic/jcompany55/java/bin/../jre/lib/amd64;D:\powerlogic\jcompany55\java\bin;c:\Program Files\Microsoft IntelliType Pro\;D:\jdk6\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\maven\bin;C:\Program Files (x86)\apache-ant-1.8.2\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\GnuWin32\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\Program Files (x86)\Git\bin;D:\powerlogic\jcompany55\eclipse; 12:33:08,731 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem 12:33:08,753 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-7) Starting remote JMX connector 12:33:08,757 INFO [org.jboss.as.remoting] (MSC service thread 1-5) Listening on /127.0.0.1:9999 12:33:08,803 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080 12:33:09,018 INFO [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final) 12:33:09,088 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) Bound data source [java:jboss/datasources/ExampleDS] 12:33:09,394 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory D:\jboss-as-web-7.0.1.Final\standalone\deployments 12:33:09,402 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found exemplo.war in deployment directory. To trigger deployment create a file called exemplo.war.dodeploy 12:33:09,403 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found hellomyfaces.war in deployment directory. To trigger deployment create a file called hellomyfaces.war.dodeploy 12:33:09,427 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 2588ms - Started 93 of 148 services (55 services are passive or on-demand) 12:33:09,444 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Starting deployment of "hellomyfaces.war" 12:33:10,229 INFO [org.jboss.as.jpa] (MSC service thread 1-8) added javax.persistence.api dependency to hellomyfaces.war 12:33:10,274 INFO [org.jboss.weld] (MSC service thread 1-5) Processing CDI deployment: hellomyfaces.war 12:33:10,628 INFO [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: hellomyfaces.war 12:33:10,652 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.2 (Final) 12:33:10,679 INFO [org.jboss.weld] (MSC service thread 1-4) Starting weld service 12:33:11,055 INFO [org.apache.myfaces.ee6.MyFacesContainerInitializer] (MSC service thread 1-6) Added FacesServlet with mappings=[/faces/*, *.jsf, *.faces] 12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true 12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true 12:33:11,096 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_CLEAR_JAVASCRIPT_FOR_BUTTON' found, using default value false 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_HIDDEN_FIELDS_FOR_LINK_PARAMS' found, using default value false 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.SAVE_FORM_SUBMIT_LINK_IE' found, using default value false 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using default value true 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_VIEWSTATE_ID' found, using default value true 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.STRICT_XHTML_LINKS' found, using default value true 12:33:11,097 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.RENDER_FORM_SUBMIT_SCRIPT_INLINE' found, using default value false 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.CONFIG_REFRESH_PERIOD' found, using default value 2 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.VIEWSTATE_JAVASCRIPT' found, using default value false 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS' found, using default value auto 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.REFRESH_TRANSIENT_BUILD_ON_PSS_PRESERVE_STATE' found, using default value false 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.VALIDATE_XML' found, using default value false 12:33:11,098 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) No context init parameter 'org.apache.myfaces.WRAP_SCRIPT_CONTENT_WITH_XML_COMMENT_TAG' found, using default value true 12:33:11,099 INFO [org.apache.myfaces.shared_impl.config.MyfacesConfig] (MSC service thread 1-6) Tomahawk jar not available. Autoscrolling, DetectJavascript, AddResourceClass and CheckExtensionsFilter are disabled now. 12:33:11,122 INFO [org.apache.myfaces.config.DefaultFacesConfigurationProvider] (MSC service thread 1-6) Reading standard config META-INF/standard-faces-config.xml 12:33:11,425 AVISO [org.apache.myfaces.config.annotation.DefaultAnnotationProvider] (MSC service thread 1-6) AnnotationConfigurator does not found classes for annotations in /WEB-INF/classes/org/jboss/test/jsf/hellomyfaces/ . This could happen because maven jetty plugin is used (goal jetty:run). Try configure org.apache.myfaces.annotation.SCAN_PACKAGES init parameter or use jetty:run-exploded instead. 12:33:11,681 INFO [org.apache.myfaces.config.DefaultFacesConfigurationProvider] (MSC service thread 1-6) Reading config : jar:file:D:%5Cjboss-as-web-7.0.1.Final%5Cmodules%5Corg%5Cjboss%5Cas%5Cweld%5Cmain%5Cjboss-as-weld-7.0.1.Final.jar!/META-INF/faces-config.xml 12:33:11,714 GRAVE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-6) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.newFactoryInstance(FactoryFinder.java:311) [myfaces-api-2.1.1.jar:] at javax.faces.FactoryFinder._getFactory(FactoryFinder.java:277) [myfaces-api-2.1.1.jar:] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:200) [myfaces-api-2.1.1.jar:] at org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:489) [myfaces-impl-2.1.1.jar:] at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:401) [myfaces-impl-2.1.1.jar:] at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:309) [myfaces-impl-2.1.1.jar:] at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) [myfaces-impl-2.1.1.jar:] at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:125) [myfaces-impl-2.1.1.jar:] at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:111) [myfaces-impl-2.1.1.jar:] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] 12:33:11,725 INFO [org.jboss.web] (MSC service thread 1-6) registering web context: /hellomyfaces 12:33:11,770 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "hellomyfaces.war" {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
6
0 / 0

[JBoss JIRA] Created: (AS7-1848) Allow configuring TransactionAttribute type for Session Bean Lifecycle methods

by Stuart Douglas (JIRA)

Allow configuring TransactionAttribute type for Session Bean Lifecycle methods ------------------------------------------------------------------------------ Key: AS7-1848 URL: https://issues.jboss.org/browse/AS7-1848 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas We need to make sure that SLSB lifecycle methods never join an existing transaction. dmlloyd: @TA would be okay by me as long as we validate the argument [10:54pm] dmlloyd: restrict it to REQUIRES_NEW or NEVER or NOT_SUPPORTED I guess [10:54pm] dmlloyd: forbid MANDATORY, SUPPORTS, and REQUIRED -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
5
0 / 0

[JBoss JIRA] (AS7-4637) Get core resources and operations out of the controller module

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4637: ------------------------------------- Summary: Get core resources and operations out of the controller module Key: AS7-4637 URL: https://issues.jboss.org/browse/AS7-4637 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server. Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff. -- 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

11 years, 5 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2012