03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Important: Although this feature is commonly referred to as the Run-as Mode,<br />

it does not have any noticeable effect on the bean to which it is applied. A<br />

bean configured to run as a member of a given security role actually executes<br />

using the identity of the caller. It is only when calling methods in other EJBs<br />

that the run as mode applies. These methods are called using the delegated<br />

identity.<br />

5.5.1 Bean level delegation<br />

The EJB 2.0 Specification defines delegation at the EJB bean level using the<br />

element which allows the application assembler to delegate all<br />

methods of a given bean to run as a member of a specific security role. At<br />

deployment time, a real user that is a member of the specified role must be<br />

mapped to this role, through a process which is called run-as role mapping. All<br />

calls to other EJBs made by the delegated bean will be called using the identity<br />

of this mapped user.<br />

Run As Caller (Default)<br />

EJB1<br />

EJB2<br />

caller01<br />

identity=caller01<br />

identity=caller01<br />

Run As Role<br />

Run As<br />

Mapping<br />

username = caller02<br />

password = xxxxxxx<br />

Role01<br />

caller01<br />

EJB1<br />

Run As Role = Role01<br />

identity=caller01<br />

EJB2<br />

identity=caller02<br />

Figure 5-8 Run as Caller versus Run as Role<br />

84 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!