[
https://jira.jboss.org/jira/browse/EJBTHREE-1756?page=com.atlassian.jira....
]
Carlo de Wolf updated EJBTHREE-1756:
------------------------------------
Workaround Description:
Use the custom principal in the calling client.
SecurityClient client = SecurityClientFactory.getSecurityClient();
client.setSimple(new CustomPrincipal("testuser"), "testpwd");
client.login();
Workaround: [Workaround Exists]
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
Affects Versions: EAP 5
Reporter: Anil Saldhana
Assignee: Carlo de Wolf
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