November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4967) Extract setting of default clustering JBossWebMetaData from TomcatDeployer

by Brian Stansberry (JIRA)

Extract setting of default clustering JBossWebMetaData from TomcatDeployer -------------------------------------------------------------------------- Key: JBAS-4967 URL: http://jira.jboss.com/jira/browse/JBAS-4967 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 Don't use TomcatDeployer as an xml-to-JBossWebMetaData pass-through for the default clustering metadata. Initially I'm going to break this out just by creating a separate deployer for it. Real solution is to have some analogue to conf/web.xml and conf/standardjboss.xml where all the default jboss-web.xml values get set. -- 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

17 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (SECURITY-88) Refactor JaasSecurityManager into JBossAuthenticationManager

by Anil Saldhana (JIRA)

Refactor JaasSecurityManager into JBossAuthenticationManager ------------------------------------------------------------ Key: SECURITY-88 URL: http://jira.jboss.com/jira/browse/SECURITY-88 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA The code that exists in JaasSecurityManager needs to be pulled into a generic delegate in JBossSX such that the JaasSecurityManager in the AS security integration as well as the default AuthenticationManager can reuse. -- 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

17 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-50) XACML EJB Layer: Role Reference Checks

by Anil Saldhana (JIRA)

XACML EJB Layer: Role Reference Checks -------------------------------------- Key: SECURITY-50 URL: http://jira.jboss.com/jira/browse/SECURITY-50 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Provide a mechanism to do EJBContext.isCallerInRole checks when xacml is enabled. -- 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

17 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-29) Validate Jacc Policy Module handles all run-as scenarios

by Anil Saldhana (JIRA)

Validate Jacc Policy Module handles all run-as scenarios -------------------------------------------------------- Key: SECURITY-29 URL: http://jira.jboss.com/jira/browse/SECURITY-29 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 With the roles being added to the security context via the mapping framework (for example), there may be cases where in run-as scenarios may not be adequately tested with the new Jacc authorization stuff. -- 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

17 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-27) Container Task:JBoss 4.2.x related Tasks for Security 2.0

by Anil Saldhana (JIRA)

Container Task:JBoss 4.2.x related Tasks for Security 2.0 --------------------------------------------------------- Key: SECURITY-27 URL: http://jira.jboss.com/jira/browse/SECURITY-27 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS. -- 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

17 years, 9 months

1
4
0 / 0

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

by Anil Saldhana (JIRA)

JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass ---------------------------------------------------------------------------------------- Key: SECURITY-28 URL: http://jira.jboss.com/jira/browse/SECURITY-28 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 JBAS-1824 -- 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

17 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1459) portal:service=TreeCache,type=hibernate should define ClusterConfig

by Galder Zamarreno (JIRA)

portal:service=TreeCache,type=hibernate should define ClusterConfig ------------------------------------------------------------------- Key: JBPORTAL-1459 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1459 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR1, 2.6.CR2, 2.4.1 SP1, 2.4.1 Final Reporter: Galder Zamarreno portal:service=TreeCache,type=hibernate omits ClusterConfig which can lead to confusion when trying to separate different AS + Portal clusters. Here's, bearing in mind the status of the JBC/HB integration, a good starting point: <attribute name="ClusterConfig"> <config> <UDP mcast_addr="${portal.hibernate.cache.udpGroup:224.0.0.36}" mcast_port="${portal.hibernate.cache.udpPort:55566}" ip_ttl="8" ip_mcast="true" mcast_send_buf_size="150000" mcast_recv_buf_size="80000" ucast_send_buf_size="150000" ucast_recv_buf_size="80000" loopback="false" up_thread="false" down_thread="false" /> <PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" /> <MERGE2 min_interval="10000" max_interval="20000" up_thread="false" down_thread="false" /> <FD_SOCK up_thread="false" down_thread="false" /> <FD shun="true" timeout="20000" max_tries="5" up_thread="false" down_thread="false" /> <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false"/> <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800" max_xmit_size="8192" discard_delivered_msgs="true" up_thread="false" down_thread="false"/> <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" up_thread="false" down_thread="false"/> <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false"/> <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true" up_thread="false" down_thread="false"/> <FRAG2 frag_size="8192" up_thread="false" down_thread="false"/> <pbcast.STATE_TRANSFER up_thread="false" down_thread="false"/> </config> </attribute> It'd be interesting to change the ClusterName as well: <attribute name="ClusterName">${portal.hibernate.cache.partition.name:portal.hibernate}</attribute> This configuration works and should be much better than the default one provided by JBossCache. -- 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

17 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (SECURITY-61) Use JBossSubject rather than JAAS Subject

by Anil Saldhana (JIRA)

Use JBossSubject rather than JAAS Subject ----------------------------------------- Key: SECURITY-61 URL: http://jira.jboss.com/jira/browse/SECURITY-61 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 The JAAS Subject is quite inflexible. There is a need for a customized Subject. Let us call it JBossSubject which can internally hold a Jaas 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-46) SASL Implementation

by Anil Saldhana (JIRA)

SASL Implementation --------------------- Key: SECURITY-46 URL: http://jira.jboss.com/jira/browse/SECURITY-46 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, JEMS Integration Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need to get an implementation of SASL for client/server kind of setup for JBoss AS. This will work off of the Security Client implementation and then security managers on the server side. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1016) Refactoring EJB 3

by Carlo de Wolf (JIRA)

Refactoring EJB 3 ----------------- Key: EJBTHREE-1016 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1016 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

17 years, 9 months

1
5
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 2007