[
https://jira.jboss.org/jira/browse/EJBTHREE-1756?page=com.atlassian.jira....
]
Paul Giblock commented on EJBTHREE-1756:
----------------------------------------
Not having custom prinicipals available in our EJBs is a major problem for us. Our users
don't just have names, but they also have an ID for which domain they are from.
Therefore, username is not unique.
Is there a workaround for this? We are currently stuck until this is fixed.
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