October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-759) Jacc layer should use the roles from the JBoss Security Manager

by Anil Saldhana (JIRA)

Jacc layer should use the roles from the JBoss Security Manager --------------------------------------------------------------- Key: EJBTHREE-759 URL: http://jira.jboss.com/jira/browse/EJBTHREE-759 Project: EJB 3.0 Issue Type: Feature Request Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD The Jacc Helper uses the principals stored in the subject for doing perm checks. There can be a need to perform role mapping on the roles. It is necessary to pick the roles from the JBoss Security Manager. We can use RealmMapping.getUserRoles to maintain compatibility with the 4.0.x series. In HEAD, ReamMapping calls internally the AuthorizationManager which will do role mapping (if user wishes) before providing the current roles. In 4.0.x, RealmMapping.getUserRoles anyway gets the roles from the authenticated subject. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=all ] Manik Surtani closed JBCACHE-664. --------------------------------- Resolution: Done > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=all ] Manik Surtani updated JBCACHE-664: ---------------------------------- Comment: was deleted > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=comments#action_12345749 ] Manik Surtani commented on JBCACHE-664: --------------------------------------- See JBQA-518 > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=comments#action_12345748 ] Manik Surtani commented on JBCACHE-664: --------------------------------------- See JBQA-508 > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-345) Add matching capabilities for Probe

by Bela Ban (JIRA)

Add matching capabilities for Probe ----------------------------------- Key: JGRP-345 URL: http://jira.jboss.com/jira/browse/JGRP-345 Project: JGroups Issue Type: Feature Request Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Optional Fix For: 2.4 JGroups/bin: ./probe.sh -match group_name=Draw ./probe.sh -match local_addr=192.168.0 Can be used to filter out unwanted responses -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBCACHE-137) Packaging of JBossCache lib

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-137?page=comments#action_12345728 ] Manik Surtani commented on JBCACHE-137: --------------------------------------- Update: References to the MarshallevValueInput/OutputStream have been updated to use the new jboss-commons-core lib, except references to MarshalledValue in JDBCCacheLoader which, for the time being, use org.jboss.aop.util.MarshalledValue. This would need to be updated once MarshalledValue is added to commons-core. > Packaging of JBossCache lib > --------------------------- > > Key: JBCACHE-137 > URL: http://jira.jboss.com/jira/browse/JBCACHE-137 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently under JBossCache module lib, there is a jboss-j2ee.jar. But in jboss-head, it was split into jboss-j2ee.jar and jboss-j2se.jar. So for example, in release 1.2.2, we have both new jars. > We will either need to update this or just get rid of the dependency totally. > Other jars which need to be revisited: > jboss-jmx.jar > jboss-minimal.jar > jboss-system.jar -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-137) Packaging of JBossCache lib

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-137?page=all ] Manik Surtani updated JBCACHE-137: ---------------------------------- Comment: was deleted > Packaging of JBossCache lib > --------------------------- > > Key: JBCACHE-137 > URL: http://jira.jboss.com/jira/browse/JBCACHE-137 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently under JBossCache module lib, there is a jboss-j2ee.jar. But in jboss-head, it was split into jboss-j2ee.jar and jboss-j2se.jar. So for example, in release 1.2.2, we have both new jars. > We will either need to update this or just get rid of the dependency totally. > Other jars which need to be revisited: > jboss-jmx.jar > jboss-minimal.jar > jboss-system.jar -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-137) Packaging of JBossCache lib

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-137?page=comments#action_12345727 ] Manik Surtani commented on JBCACHE-137: --------------------------------------- >From Ben: Here is the current dependency: 1. jboss-comm.jar: org.jboss.util.NestedRuntimeException 2. jboss-jmx.jar: org.jboss.mx.util.JBossNotificationBroadcastSupport 3. jboss-system.jar: ServiceMBeanSupport 4. jboss-j2ee.jar: javax.transaction.* 5. jboss-minimal.jar: org.jboss.ivocation.MarshalledValue* > Packaging of JBossCache lib > --------------------------- > > Key: JBCACHE-137 > URL: http://jira.jboss.com/jira/browse/JBCACHE-137 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently under JBossCache module lib, there is a jboss-j2ee.jar. But in jboss-head, it was split into jboss-j2ee.jar and jboss-j2se.jar. So for example, in release 1.2.2, we have both new jars. > We will either need to update this or just get rid of the dependency totally. > Other jars which need to be revisited: > jboss-jmx.jar > jboss-minimal.jar > jboss-system.jar -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-163) Consolidate jboss related libraries

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-163?page=all ] Manik Surtani closed JBCACHE-163. --------------------------------- Resolution: Duplicate Issue > Consolidate jboss related libraries > ----------------------------------- > > Key: JBCACHE-163 > URL: http://jira.jboss.com/jira/browse/JBCACHE-163 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently the jboss dependent packaging in JBossCache is a bit scattered. We use the packaging from jboss-head but they are different the packaing, say, jboss-4.0. > For example, jboss head recently split jboss-j2ee.jar into jboss-j2ee and jboss-j2se.jar of which has no interests to us at all. > Nonetheless, our dependency on jboss is very minimal now. So maybe we should think of consolidating all the jboss packaging into a single one? In theory, we should use the jboss packages from full release, like AS4.0.2. -- 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, 7 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 October 2006