Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.4.9.CR1, 7.4.9.GA
Affects Version/s: 7.4.7.GA
Component/s: Security
Labels:
- regression_test_only

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
-
Target Release:

7.4.z.GA
Git Pull Request:
https://github.com/wildfly-security/soteria/pull/2
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The JSR 345: Enterprise JavaBeans 3.2 specification defines that propagation must behave exactly the same behavior between sync and async. When using the SecurityContext.getCallerPrincipal, the used Eclipse Soteria implementation of the Java EE Security API Specification is delegating to EJBContext.getCallerPrincipal which obtains the custom principal correctly. This principal is returned only if it is of CallerPrincipal type. This fix is to return the principal from EJBContext whether it is of type CallerPrincipal or not.

clones

WFLY-17316 SecurityContext callerPrincipal not set with Asynchronous tagged EJB

Closed

is cloned by

JBEAP-24200 [GSS](8.0.z) SecurityContext callerPrincipal not set with Asynchronous tagged EJB

Closed

is incorporated by

JBEAP-24207 (7.4.z) Upgrade Soteria from 1.0.1.redhat-00002 to 1.0.1.redhat-00003

Closed

Assignee:: Diana Krepinska

Reporter:: Joerg Baesner

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2022/11/18 2:01 PM

Updated:: 2023/01/11 10:20 AM

Resolved:: 2022/12/02 6:47 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates