February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-673) copy feature: abillity to copy a package or an asset

by Michael Neale (JIRA)

copy feature: abillity to copy a package or an asset ---------------------------------------------------- Key: JBRULES-673 URL: http://jira.jboss.com/jira/browse/JBRULES-673 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-658) bug in oneway thread pool under heavy load

by Tom Elrod (JIRA)

bug in oneway thread pool under heavy load ------------------------------------------ Key: JBREM-658 URL: http://jira.jboss.com/jira/browse/JBREM-658 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.2.0.Alpha4, 1.4.5.GA Reporter: Tom Elrod Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Per forum thread, there looks to be a bug in concurrent lib (deadlock in BlockedLinkedQueue). Will either need to look for a newer version with fix or a replacement for the default thread pool being used for oneway invocations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-696) ClassCastException for ShadowProxies when using hirarchy of classes

by Edson Tirelli (JIRA)

ClassCastException for ShadowProxies when using hirarchy of classes ------------------------------------------------------------------- Key: JBRULES-696 URL: http://jira.jboss.com/jira/browse/JBRULES-696 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.1-m1 Reporter: Edson Tirelli Assigned To: Edson Tirelli Priority: Critical Fix For: 3.1-m2 The core engine is raising ClassCastExceptions when a fact is asserted and there are rules matching different classes in this fact hirarchy, possibly assigning a shadow proxy for it that is not the most specialized proxy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ] Anil Saldhana resolved JBAS-1824. --------------------------------- Resolution: Done Configuration: The presence of a tag "<jacc-star-role-allow>" in jboss-web.xml makes the web container to generate a WebResourcePermission(uri, null) perm added to the "*" role. Now it is upto the JACC policy provider to bypass authorization based on this perm. ------------------- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd"> <jboss-web> <security-domain>java:/jaas/userinrole</security-domain> <jacc-star-role-allow>true</jacc-star-role-allow> </jboss-web> ------------------------------------ An example of a test jacc policy that does this is: http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/testsuite/src/... > JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass > ---------------------------------------------------------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Fix For: JBossAS-4.2.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ] Anil Saldhana updated JBAS-1824: -------------------------------- Fix Version/s: JBossAS-4.2.0.CR1 (was: JBossAS-4.2.1.CR1) ---------------------------------------------------------------------------------------------------------------------------------------- asaldhana~/jboss-4.2/testsuite>ant tests-jacc-security-allstarrole Buildfile: build.xml tests-jacc-security-allstarrole: [echo] creating jacc-security-allstarrole config [echo] Overwriting config descriptors [copy] Copying 7 files to C:\cygwin\home\asaldhana\jboss-4.2\build\output\jboss-4.2.0.CR1\server\jacc-security-allstarrole [server:start] Starting server "jacc-security-allstarrole" with command: [server:start] C:\Java\jdk1.5.0_10\bin\java -cp C:\cygwin\home\asaldhana\jboss-4.2\build\output\jboss-4.2.0.CR1\bin\run.jar;c:\java\jdk1.5.0_10\lib\tools.jar org.jboss.Main -c jacc-security-allstarrole -b localhost Overriding previous definition of reference to jacc-tests-props [echo] Starting patternset=jacc.allstarrole.includes config=jacc-security-allstarrole [junit] Running org.jboss.test.jacc.test.allstarrole.JBAS1824AllStarRoleJaccTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.688 sec [echo] Will stop the jboss instance at url jnp://localhost:1099 [java] The jvmargs attribute is deprecated. Please use nested jvmarg elements. [java] Shutdown message has been posted to the server. [java] Server shutdown may take a while - check logfiles for completion [echo] Waiting for 'jacc-security-allstarrole' server to stop... BUILD SUCCESSFUL Total time: 27 seconds asaldhana~/jboss-4.2/testsuite> ----------------------------------------------------------------------------------------------------------------------------------------------- > JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass > ---------------------------------------------------------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Fix For: JBossAS-4.2.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-180) Security redeployment problem

by Ryszard Kozmik (JIRA)

Security redeployment problem ----------------------------- Key: JBFORUMS-180 URL: http://jira.jboss.com/jira/browse/JBFORUMS-180 Project: JBoss Forums Issue Type: Bug Components: Portlet Productization Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Minor Fix For: 1.0.0 RC There is a problem with redeployment. Security seems to have problems with it and doesn't work properly later. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1260) Incorrect parsing of dates in UserContextConverter

by Chris Laprun (JIRA)

Incorrect parsing of dates in UserContextConverter -------------------------------------------------- Key: JBPORTAL-1260 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1260 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 I wish Java would provide a DateFormat accepting xsd:dateTime... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-162) Consider implementing different message delivery optimisations

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-162?page=all ] Tim Fox closed JBMESSAGING-162. ------------------------------- Resolution: Duplicate Issue > Consider implementing different message delivery optimisations > -------------------------------------------------------------- > > Key: JBMESSAGING-162 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-162 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Consideri implementing different different message delivery optimisations. > e.g. client side buffering > multicast (both reliable and unreliable) > these could be selected by using special, jboss specific ack modes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-246) Optimise browsing

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-246?page=all ] Tim Fox closed JBMESSAGING-246. ------------------------------- Resolution: Duplicate Issue > Optimise browsing > ----------------- > > Key: JBMESSAGING-246 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-246 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently browsing is inefficient and copies the entire set of message references. Instead we should use the deque iterator + the deliveries iterator. > We should also investigate activating the browsing interceptor to batch messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-307) Down cache optimisation

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-307?page=all ] Tim Fox closed JBMESSAGING-307. ------------------------------- Resolution: Duplicate Issue > Down cache optimisation > ----------------------- > > Key: JBMESSAGING-307 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-307 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db > and just transfer from the downcache to the in memory list when loading -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 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 February 2007