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.

These unprotected methods can have one of three permissions applied:<br />

1. Uncheck. This is the default, and indicates that unprotected methods should<br />

be left unprotected. Anyone can call these methods.<br />

2. Exclude. Unprotected methods are unavailable to all callers.<br />

3. Role. Unprotected methods are available only to members of a specific<br />

security role.<br />

Figure 5-5 Assigning roles to unprotected EJB methods<br />

Note: This behavior is different than in previous <strong>WebSphere</strong> versions. In<br />

<strong>WebSphere</strong> Application Server Version 4, the default was to grant access to<br />

all EJB methods when no methods were explicitly protected, and to deny<br />

access to all EJB methods (by default) when at least one EJB method was<br />

protected.<br />

Most importantly, the default in Version 5 is for methods that are not explicitly<br />

unprotected to be unchecked.<br />

5.4 <strong>Security</strong> role references<br />

<strong>Security</strong> role references are used to provide a layer of indirection between<br />

security roles named in EJB Java code and security roles that are defined at<br />

application assembly time. This allows security roles names to be modified<br />

without requiring changes in the application code.<br />

80 <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!