November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2585?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2585: ---------------------------------------- In addition to the access control related changes thoroughly check additional places where the current AccessControlContext is obtained within a PriviledgedAction. Some places may want a clean AccessControlContext that looses the information about the caller, others may genuinely want the current AccessControlContext but instead accidentally replace it. > Correct the identification of the current caller when a security manager is enabled. > ------------------------------------------------------------------------------------ > > Key: WFLY-2585 > URL: https://issues.jboss.org/browse/WFLY-2585 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-354) Can't load pom.properties when jar not on default drive on Windows

by Peter Cooper (JIRA)

Peter Cooper created DROOLS-354: ----------------------------------- Summary: Can't load pom.properties when jar not on default drive on Windows Key: DROOLS-354 URL: https://issues.jboss.org/browse/DROOLS-354 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: Windows Reporter: Peter Cooper Assignee: Mark Proctor I'm using Apache Tomcat to run my web application, which includes Drools 6.0.0.Final and getting rules files out of the classpath. However, the webapps directory (the appBase in Tomcat's server.xml) is on a different drive than the main Tomcat installation. When Drools is trying to get its pom properties (ClasspathKieProject's getPomProperties method, starting on line 167) it looks like it first strips off the Windows drive letter. It then tries to find the path, but on the drive of the Windows current directory (in this case, the drive where Tomcat is installed) instead of the drive where the file actually is. This means that it can't find the jar file, so I get the "Unable to load pom.properties" "as jarPath cannot be found" error. I'm not sure why it's trying to strip off the drive letter, since I think it would be able to find the file correctly if that weren't the case. Thank you. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1119) IronJacamar 1.1.2.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1119?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1119. ------------------------------------ Resolution: Done > IronJacamar 1.1.2.Final > ----------------------- > > Key: JBJCA-1119 > URL: https://issues.jboss.org/browse/JBJCA-1119 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.1.2.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2480) Infinispan test XML files do not validate against XSD yet are parsed ok

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2480?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-2480: --------------------------------- Priority: Minor (was: Major) > Infinispan test XML files do not validate against XSD yet are parsed ok > ----------------------------------------------------------------------- > > Key: WFLY-2480 > URL: https://issues.jboss.org/browse/WFLY-2480 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.Final > > > So one or the other should to change. > cvc-complex-type.2.4.a: Invalid content was found starting with element 'store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected. > cvc-complex-type.2.4.a: Invalid content was found starting with element 'mixed-keyed-jdbc-store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected. > cvc-complex-type.2.4.d: Invalid content was found starting with element 'binary-keyed-table'. No child element is expected at this point. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1477) JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications

by Frank Cornelis (JIRA)

[ https://issues.jboss.org/browse/WFLY-1477?page=com.atlassian.jira.plugin.... ] Frank Cornelis commented on WFLY-1477: -------------------------------------- OK, I didn't notice the Component being set to JBoss Web. So yes, there seems to be a similar issue with Undertow. > JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1477 > URL: https://issues.jboss.org/browse/WFLY-1477 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (JBoss Web) > Affects Versions: 8.0.0.Alpha1 > Environment: CentOS 6.x, JBoss AS 7.1.1.Final > Reporter: Steve S > Assignee: Remy Maucherat > Labels: domain, jaas, jboss, jbossweb, login, module, security > > Please see the following forum post for a detailed explanation and findings(and potential workaround): > https://community.jboss.org/message/822054#822054 > If multiple WARs are deployed that depend on a login module leveraging: > HttpServletRequest request = (HttpServletRequest)PolicyContext.getContext("javax.servlet.http.HttpServletRequest"); > then upon undeploy of any web application in the container the HttpServletRequestPolicyContextHandler is removed(deregistered) in the stop() lifecycle method of the JBossWebRealmService, resulting in: > 13:03:35,335 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (ajp--0.0.0.0-8009-1) Login failure: javax.security.auth.login.LoginException: java.lang.IllegalArgumentException: No PolicyContextHandler for key=javax.servlet.http.HttpServletRequest at javax.security.jacc.PolicyContext.getContext(PolicyContext.java:117) > for any webapps still deployed for every subsequent access to them. > Simply redeploying any ONE of the remaining webapps or the previously undeployed webapp causes this problem to go away for all deployed applications. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2585?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2585: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1034700, https://bugzilla.redhat.com/show_bug.cgi?id=1035231 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1034700) > Correct the identification of the current caller when a security manager is enabled. > ------------------------------------------------------------------------------------ > > Key: WFLY-2585 > URL: https://issues.jboss.org/browse/WFLY-2585 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2585?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2585: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1034700, https://bugzilla.redhat.com/show_bug.cgi?id=1035231, https://bugzilla.redhat.com/show_bug.cgi?id=1035232 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1034700, https://bugzilla.redhat.com/show_bug.cgi?id=1035231) > Correct the identification of the current caller when a security manager is enabled. > ------------------------------------------------------------------------------------ > > Key: WFLY-2585 > URL: https://issues.jboss.org/browse/WFLY-2585 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1477) JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/WFLY-1477?page=com.atlassian.jira.plugin.... ] Remy Maucherat commented on WFLY-1477: -------------------------------------- Well, the bug is assigned to JBoss Web, not Undertow, and was real (it got fixed in the web subsystem). So if something is wrong about undertow in Wildfly, it is a different issue. > JACC HttpServletRequestPolicyContextHandler removal on single application undeploy impacting all other deployed applications > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1477 > URL: https://issues.jboss.org/browse/WFLY-1477 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (JBoss Web) > Affects Versions: 8.0.0.Alpha1 > Environment: CentOS 6.x, JBoss AS 7.1.1.Final > Reporter: Steve S > Assignee: Remy Maucherat > Labels: domain, jaas, jboss, jbossweb, login, module, security > > Please see the following forum post for a detailed explanation and findings(and potential workaround): > https://community.jboss.org/message/822054#822054 > If multiple WARs are deployed that depend on a login module leveraging: > HttpServletRequest request = (HttpServletRequest)PolicyContext.getContext("javax.servlet.http.HttpServletRequest"); > then upon undeploy of any web application in the container the HttpServletRequestPolicyContextHandler is removed(deregistered) in the stop() lifecycle method of the JBossWebRealmService, resulting in: > 13:03:35,335 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (ajp--0.0.0.0-8009-1) Login failure: javax.security.auth.login.LoginException: java.lang.IllegalArgumentException: No PolicyContextHandler for key=javax.servlet.http.HttpServletRequest at javax.security.jacc.PolicyContext.getContext(PolicyContext.java:117) > for any webapps still deployed for every subsequent access to them. > Simply redeploying any ONE of the remaining webapps or the previously undeployed webapp causes this problem to go away for all deployed applications. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2585?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2585: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1034700 > Correct the identification of the current caller when a security manager is enabled. > ------------------------------------------------------------------------------------ > > Key: WFLY-2585 > URL: https://issues.jboss.org/browse/WFLY-2585 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2585) Correct the identification of the current caller when a security manager is enabled.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2585: -------------------------------------- Summary: Correct the identification of the current caller when a security manager is enabled. Key: WFLY-2585 URL: https://issues.jboss.org/browse/WFLY-2585 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 8.0.0.CR1 -- 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

12 years, 8 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 November 2013