[
https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFLY-9240:
----------------------------------------
Thanks, in that case then it looks like this commit may have been the trigger for this
regression: -
https://github.com/wildfly/wildfly/commit/f86fe14068e3cff4ab7e304707a0426...
So the fix I am going to apply to Elytron will correct the NPE.
FYI for bug reports in the future it would help greatly if a clearly visible error and
stack trace is available in the test output if it could be included in the bug report
somewhere, from the stack trace it has been a fairly simple step to look into the code and
commit histories to find out what is happening but to get there I have needed to clone and
build two separate repositories.
WeldSecurityServices not able to obtain the current SecurityDomain
anymore
--------------------------------------------------------------------------
Key: WFLY-9240
URL:
https://issues.jboss.org/browse/WFLY-9240
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, Security
Affects Versions: 11.0.0.Beta1, 11.0.0.CR1
Reporter: Martin Kouba
Assignee: Darran Lofthouse
Priority: Critical
The integration code used by Weld 3 to propagate the security context of the current
thread to different threads (needed for async events CDI 2.0 feature) is not able to
obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
The invocation of
[
SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...]
returns {{null}}.
Note that this worked on WildFly *11.0.0.Alpha1*.
It's also possible that the test (see also steps to reproduce) is wrong. A
review/help from a security expert would be appreciated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)