-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
AS 4.2.1.GA
-
None
-
Workaround Exists
-
Having a secured bean with a timeout method with @PermitAll, but without an unauthenticatedIdentity will lead to a 'random' identity being used to call the method or no identity at all. The last one leads to EJBAccessExceptions.
Spec 18.2.2:
"Since the timeout callback method is an internal method of the bean class, it has no client security context. When getCallerPrincipal is called from within the timeout callback method, it returns the container's representation of the unauthenticated identity."
We must disallow all calls to a timeout method if unauthenticatedIdentity is not set.
- is related to
-
EJBTHREE-1891 ServiceContainer may not be popping the Principal
- Resolved
- relates to
-
EJBTHREE-1036 TimeOut method callback should bypass security as it has no security context
- Open