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.

This scenario would operate as follows:<br />

1. The client constructs a SOAP message and sends it to a Web Service.<br />

2. The message passes through a firewall prior to arriving to the Web Service.<br />

3. The firewall examines the security token(s) and signatures in the <br />

header.<br />

4. The firewall makes an assessment of the validity of the message and possibly<br />

using external data, makes a determination as to whether or not to authorize<br />

the message passing through the firewall.<br />

When the SOAP message is without any encryption, the firewall can examine the<br />

message headers for authorization, but what if it is encrypted? For end-to-end<br />

security, SOAP message is encrypted. However, a message can still be validated<br />

as follows:<br />

1. After signing and encrypting the message, the client adds an additional<br />

header with the firewall listed as the SOAP actor. Into this header<br />

block the client places a element containing a signature over<br />

the encrypted data. Also, using , the signature is<br />

prepended.<br />

2. From the header, the firewall reads and validates the security<br />

token and signature.<br />

3. The firewall then makes a determination, possibly using external data, as to<br />

whether or not to authorize the message to pass through the firewall.<br />

7.1.4 <strong>Security</strong> with the Web Services Gateway<br />

<strong>WebSphere</strong> Web Services GateWay is bundled with <strong>WebSphere</strong> Application<br />

Server V5 Network Deployment package. After installing Network Deployment,<br />

we need to install the wsgw.ear and wsgwsoap1.ear on the application server.<br />

Gateway <strong>Security</strong> Implementation<br />

Web Services GateWay provides HTTP Basic Authentication and an<br />

authorization mechanism based upon the security features provided by<br />

<strong>WebSphere</strong> Application Server.<br />

Important: Gateway-level authentication must be enabled for enabling<br />

operational-level authentication. You must do the same even before installing<br />

channels. When we enable gateway-level authentication, filters will have<br />

access to the request’s authentication information.<br />

Chapter 7. Securing Enterprise Integration components 155

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

Saved successfully!

Ooh no, something went wrong!