[
https://issues.jboss.org/browse/WFLY-11604?page=com.atlassian.jira.plugin...
]
Diana Vilkolakova commented on WFLY-11604:
------------------------------------------
{quote} I think we should get an issue created to see if there is a way to fix this for
the Elytron case without breaking the fix for JBEAP-9744.{quote} I created an issue
WFLY-12537 for this purpose.
I also created WFLY-12538 to address the fact that scenario #1 returns
'non-anonymous' principal when Elytron is enabled, which is incorrect. I am
closing this issue since it is superceded by WFLY-12537 and WFLY-12538.
Non-anonymous principal is not propagated from EJB context to CDI
bean
----------------------------------------------------------------------
Key: WFLY-11604
URL:
https://issues.jboss.org/browse/WFLY-11604
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, Security
Affects Versions: 14.0.1.Final, 15.0.1.Final
Reporter: Nikoleta Ziakova
Priority: Critical
This is a follow-up on WFLY-11587 which only dealt with being able to inject the
principal.
However, during testing I have tried a scenario when the caller principal was not
anonymous (run-as-principal setting in jboss-ejb3.xml). See the test case in this
[
commit|https://github.com/nziakova/wildfly/commit/9ae586ad0159e6399f65103...].
The principal is not propagated from the EJB context. The result is that injected
principal in the CDI bean is always anonymous, although {{ctx.getCallerPrincipal()}} in
the EJB returns correct principal.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)