-
Bug
-
Resolution: Done
-
Critical
-
7.1.4.GA
WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
Using WildFlyInitialContextFactory and calling a remote EJB server.
Observations:
1) If the ejb lookup is "reproducer/TestSLSB!test.Test" (basically like a RemoteNaming lookup), the ejb is invoked successfully, but the caller is seen as anonymous instead of the ejbuser which is specified in the Context properties.
Using the ejb-client type lookup: ejb:/reproducer/TestSLSB!test.Test , then it shows up as ejbuser as expected
2) if a client creates 2 InitialContexts and uses the lookup reproducer/TestSLSB!test.Test" on ctx1 , then uses the lookup "ejb:/reproducer/TestSLSB!test.Test " on ctx2 in that order, then they both show anonymous (as if it uses only the context that was created first).
If you switch the order, and use ejb:/reproducer/TestSLSB!test.Test first, then they both show ejbuser
- clones
-
WFLY-10997 WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
- Resolved
- is cloned by
-
JBEAP-15279 [GSS](7.1.z) WildFlyInitialContextFactory EJB proxy security behavior inconsistent with different context lookups
- Closed
- is incorporated by
-
JBEAP-15617 (7.2.z) Upgrade WildFly Core from 6.0.11 to 6.0.12
- Closed
- is related to
-
JBEAP-10320 Elytron outflow-security-domains doesn't work for Servlet-to-EJB calls
- Closed