[jboss-jira] [JBoss JIRA] Commented: (JBAS-4423) EJB3 Security Integration Assimilation with JBoss Security
[ http://jira.jboss.com/jira/browse/JBAS-4423?page=comments#action_12375728 ]
Anil Saldhana commented on JBAS-4423:
-------------------------------------
This is on going. The ejb3 security work does not affect the other work that is happening
in the ejb3 world. I am in constant touch with carlo and BillD.
I have finished all the major portions of this. There is one issue with mdbs that I cannot
work on yet because of some JNDI lookup errors that are happening due to ejb3/messaging
regression. Carlo/Bill know about it. Once that gets resolved, I would say a couple of
hours from my side to resolve the mdb security context issue.
As and when any issues are brought to my attention, I promptly fix them such that the tck
work proceeds.
EJB3 security alignment will be an ongoing work until the unified meta data comes out and
ejb3 meta data gets aligned with it.
This is why this JIRA issue is not resolved yet. Please ask Scott/Adrian for further
information.
EJB3 Security Integration Assimilation with JBoss Security
----------------------------------------------------------
Key: JBAS-4423
URL: http://jira.jboss.com/jira/browse/JBAS-4423
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Security, EJB3
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
There is a need for immediate alignment of the EJB3 security layer with ejb2 security.
There may be a need for some abstraction to be pulled out in the JBoss Security
SPI/Implementation layer.
--
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