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: EJB
Labels:
- test_included

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/jbossas/jboss-eap7/pull/4412
Intelligence Requested:
Market:

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

Currently, attempting to propagate an identity from a servlet within one deployment to an EJB within another deployment associated with a different security domain fails even when outflow-security-domains and trusted-security-domains are configured. The underlying problem is that outflow is not actually triggered in this case. To activate any outflow identities automatically, one option is to add a global EJB client interceptor that would ensure that we always runAs the current security identity.

depends on

JBEAP-24227 [GSS](7.4.z) WFCORE-6108 - Add a new Phase constant to install global EJB client interceptors

Closed

JBEAP-24167 (7.4.z) Upgrade WildFly Core from 15.0.19.Final-redhat-00001 to 15.0.21.Final-redhat-00002

Closed

incorporates

WFLY-17254 Add a global EJB client interceptor for EJB deployments that will runAs the current security identity to activate any outflow identities

Closed

Assignee:: Farah Juma

Reporter:: Brad Maxwell

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2022/11/28 3:43 PM

Updated:: 2024/08/19 2:11 PM

Resolved:: 2022/12/17 5:22 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates