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

Create successful ePaper yourself

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

Outside World<br />

Demilitarized Zone<br />

(DMZ)<br />

Internal Network<br />

Public Key<br />

Infrastructure<br />

Directory &<br />

<strong>Security</strong><br />

Server<br />

Registry<br />

data<br />

IP Network<br />

Protocol firewall<br />

<strong>Security</strong><br />

Proxy<br />

Domain firewall<br />

Application<br />

Servers<br />

Client<br />

Existing<br />

application<br />

and data<br />

Client<br />

Tier<br />

Single<br />

Sign-On<br />

Application 1<br />

Application 2<br />

Figure 11-5 Web Single Sign-On (heterogeneous applicaiton servers) runtime pattern<br />

Another decision that was made was to use credential propagation from the<br />

Web-tier down to the business logic tier and back-end applications. This will<br />

enable non-repudiation of back-end transactions initiated by Web users. We can<br />

achieve this by using the same security server to manage the Web tier and<br />

business logic and back-end applications. No credential mapping or<br />

transformation is required; this might be an option if separate security<br />

mechanisms were used in different application tiers. The security context is<br />

presented all the way from the Web down to the back-end resources.<br />

This approach significantly simplifies users’ and policy management by unifying<br />

the user profile across the entire business process supported by the Web<br />

application. It doeas requires some complex configurations and usage of security<br />

servers that are supported by the chosen application servers.<br />

Chapter 11. <strong>Security</strong> in Patterns for e-business 359

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

Saved successfully!

Ooh no, something went wrong!