Modified EJB Method Privileges Do Not Get Applied For Existing Remote Clients (Doc ID 979168.1)

Last updated on FEBRUARY 24, 2017

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.0.0 to 10.1.3.5.0 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.

Symptoms

Existing remote clients do not get aware about modified EJB method permissions.

Problem Scenario (Test Case)

Oc4J has groups "RoleA" and RoleB" defined.
User "demo" is member of "RoleA"

A session bean has two methods:

@DeclareRoles({"RoleA","RoleB"})
@Stateless(name="MySessionEJB")
public class MySessionEJBBean implements MySessionEJB, MySessionEJBLocal {
  public MySessionEJBBean() {
}
@RolesAllowed("RoleA")
public String executeOnlyRoleA() {
  return "executeOnlyeRoleA called";
}

@RolesAllowed("RoleB")
public String executeOnlyRoleB() {
  return "executeOnlyeRoleB called";
}

executeOnlyRoleA() can only be called by members of "RoleA".
executeOnlyRoleB() can only be called by members of "RoleB".

A remote client calls executeOnlyRoleA() as user "demo" which is member of "RoleA".
-> This call is successful.

The client waits for user hitting a key (System.in.read();).
The the administrator adds "RoleB" to user "demo".
The client user hits a key to let the client resume.
The client application calls executeOnlyRoleB().
-> client fails with:
OracleRemoteException: demo is not allowed to call this EJB method, check your security settings (method-permission in ejb-jar.xml and security-role-mapping in orion-application.xml).


After restarting the client application both methods can be executed successfully.

Using a connection-timeout as described in <> does resolve the problem.
A new connection is able to use the new state of the privileges.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms