[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1756) EJB3: EJBContext getCallerPrincipal does not see the custom principal
Chris Imershein (JIRA)
jira-events at lists.jboss.org
Mon Aug 24 14:52:24 EDT 2009
[ https://jira.jboss.org/jira/browse/EJBTHREE-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12482490#action_12482490 ]
Chris Imershein commented on EJBTHREE-1756:
-------------------------------------------
Could this be related at all to #JBAS-7037 ?
https://jira.jboss.org/jira/browse/JBAS-7037
In any case, if 1756 could be put onto the road map for JBAS at some time, that would be appreciated.
Notes in the JBoss Forum thread suggest a possible issue regarding JBossWebRealm.authenticate, SubjectInfo, and CredentialIdentity -- however a "workaround" indicates the custom principal can be retrieved from the RealmMapping inside EJBContextImpl (but only after using reflection to access a private implementation field).
A stack-overflow question has also been created for a similar issue:
http://stackoverflow.com/questions/1295938/jaas-and-jboss-5-problem-with-principal
> EJB3: EJBContext getCallerPrincipal does not see the custom principal
> ---------------------------------------------------------------------
>
> Key: EJBTHREE-1756
> URL: https://jira.jboss.org/jira/browse/EJBTHREE-1756
> Project: EJB 3.0
> Issue Type: Bug
> Components: Security
> Reporter: Anil Saldhana
> Assignee: Anil Saldhana
> Attachments: CustomPrincipal.zip
>
>
> Forum thread reports a case where custom principal in the Login Module is not being propagated to the EJBContext getCallerPrincipal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list