[
https://jira.jboss.org/browse/EJBTHREE-754?page=com.atlassian.jira.plugin...
]
Carlo de Wolf resolved EJBTHREE-754.
------------------------------------
Resolution: Out of Date
This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.
If you can reproduce this bug against a currently maintained version of
JBoss EJB 3 please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
isCallerInRole checks should go through JACC layer (if JACC is
configured)
--------------------------------------------------------------------------
Key: EJBTHREE-754
URL:
https://jira.jboss.org/browse/EJBTHREE-754
Project: EJB 3.0
Issue Type: Task
Components: Security
Affects Versions: EJB 3.0 RC9 - FD
Reporter: ANIL SALDHANA
Assignee: Scott M Stark
Fix For: Branch_4_2
Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to
Scott.
The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has
configured jacc. I am not sure what the best way to tell the xxxContext layer to use jacc
helper if user desires. Maybe a simple system property may do it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira