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
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
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
Default SFSB timeout should be longer than the default tomcat HttpSession timeout.
----------------------------------------------------------------------------------
Key: EJBTHREE-788
URL: http://jira.jboss.com/jira/browse/EJBTHREE-788
Project: EJB 3.0
Issue Type: Bug
Reporter: Gavin King
Priority: Critical
This bites every user who tries to use Seam.
--
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
Create a canonical "JndiServiceMBeanSupport" useful for binding objects to JNDI
-------------------------------------------------------------------------------
Key: JBAS-3767
URL: http://jira.jboss.com/jira/browse/JBAS-3767
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMX
Reporter: Elias Ross
Assigned To: Scott M Stark
A common application integration pattern is to create MBean services that bind objects (or themselves) to JNDI.
These objects bound to JNDI are then used in EJBs.
It seems generally useful to provide a class with JBoss, similar to ServiceMBeanSupport, which allows users to bind objects to the local JNDI.
A lot of JBoss services do bind objects to JNDI and could probably extend from this base class.
http://wiki.jboss.org/wiki/Wiki.jsp?page=BindMBeanToJNDI
Additional ideas: Create an attribute "BindObject". Then users could do something like:
<attribute name="BindObject" attributeClass="..."
serialDataType="javaBean">
</attribute>
--
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
minimize/maximize causes portlet to return to initial state
-----------------------------------------------------------
Key: JBPORTAL-1055
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1055
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Server
Affects Versions: 2.4 Final
Environment: CentOS release 4.4 (Final), jdk1.5.0_06
Reporter: Johnny Healey
Assigned To: Julien Viet
This has been noticed in a handful of custom portlets, but can be duplicated in the "event test" page that ships with the portal. "Test Event A" can change the color of the text in "Test Event B", but minimizing or maximizing "Test Event B" causes the text to return to the original color, black.
--
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
Jboss Portal to support virtual hosts
-------------------------------------
Key: JBPORTAL-1004
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1004
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Sverker Abrahamsson
JBoss Portal is today unable to support multiple virtual hosts, i.e. it's not possible to create a portal bound to the address www.foo.com and one that is bound to www.bar.com.
This is a major problem for real world usage of JBoss Portal
--
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
Optimise browsing
-----------------
Key: JBMESSAGING-877
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-877
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
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
Consider using multicast or reliable multicast for message delivery
-------------------------------------------------------------------
Key: JBMESSAGING-878
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-878
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
We could use multicast or jgroups reliable multicast for delivery of messages from server to client when there are many subscribers - currently this is point to point.
--
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