29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> provides a default audit service provider and<br />

event factory 2 , but you can change them if you have special needs. For instance,<br />

you could configure a third-party audit service provider to record the generated<br />

events to a different repository.<br />

12.3 Security configuration considerations<br />

When planning for security, it is important to keep in mind the difference between<br />

administrative security and application security from the <strong>WebSphere</strong> perspective:<br />

► Administrative security protects the cell from unauthorized modification.<br />

► <strong>Application</strong> security enables security for the applications in your environment.<br />

This type of security provides application isolation and requirements for<br />

authenticating application users.<br />

In previous releases of <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong>, when a user enabled<br />

global security, both administrative and application security were enabled. Since<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> V6.1, these security functions can be enabled<br />

separately. Administrative security can be enabled during profile creation. The<br />

default is for administrative security to be enabled. <strong>Application</strong> security is<br />

disabled, by default, and must be enabled after profile creation using the<br />

administrative tools. To enable application security, you must also enable<br />

administrative security.<br />

When a new application server profile or deployment manager profile is created,<br />

you have the following options for administrative security:<br />

► Use <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> to manage user identities and the<br />

authorization policy (file-based repository).<br />

► Do not enable security.<br />

► Use a z/OS security product to manage user identities and authorization<br />

policy (z/OS only).<br />

The default authentication mechanism is LTPA, but when Kerberos is included in<br />

the product, you can select Kerberos and LTPA later.<br />

2 The audit service provider formats and records audit events. The event factory collects the data<br />

associated to the auditable security events and sends it to the audit service provider.<br />

402 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

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

Saved successfully!

Ooh no, something went wrong!