22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - 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.

590 Lotus Security Handbook<br />

beneficial because it does not require the users to learn a new username and<br />

password.<br />

<strong>Redbooks</strong>Co implements the WebSphere Portal portlets for the new learning and<br />

messaging capabilities, such that users can link directly to these new capabilities<br />

from within the corporate portal enabled in the previous phase.<br />

Figure 13-7 Lotus Learning Management System portlets<br />

13.7 Stage 6: Further securing remote access<br />

At this point, <strong>Redbooks</strong>Co has encrypted communications between users and<br />

servers over the Internet and the private corporate LAN via SSL and the reverse<br />

proxy solution. They also have a single corporate LDAP directory that controls<br />

authentication names and passwords, and performs password management<br />

functions like enforcing password length and password age rules. While this<br />

system is quite secure, users are passed through the reverse proxy server to the<br />

backend WebSphere Portal, Lotus servers, or both prior to being authenticated.<br />

It is up to the backend systems to ensure authentication and access rights to<br />

their services.<br />

The <strong>Redbooks</strong>Co IT manager decides that he would like to identify whether<br />

users are even allowed to pass through the reverse proxy before they are<br />

allowed to communicate with the backend servers. He wants the reverse proxy to<br />

be more than just a relay device, but a gatekeeper device as well. He decides to<br />

implement an enterprise access control system via <strong>IBM</strong> Tivoli Access Manager<br />

(TAM). The proper plug-in for the reverse proxy enables the reverse proxy to

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

Saved successfully!

Ooh no, something went wrong!