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.

Figure 14-21 Firewall rules<br />

14.3 Introduction of an “enterprise” LDAP server<br />

610 Lotus Security Handbook<br />

During the initial phases of this scenario, an existing Domino server and Domino<br />

Directory were enabled for LDAP, and provided authentication capabilities via<br />

LDAP. In this phase, a separate “enterprise” LDAP server is introduced, moving<br />

the authentication capabilities of this infrastructure to an independent LDAP<br />

platform in preparation for the introduction of non-Lotus technologies. While<br />

LDAP functionalities could have been left in Domino, and all additional phases<br />

would still work, the Redbook team felt that the use of a non-Lotus LDAP server<br />

would more accurately simulate most enterprise environments.<br />

Furthermore, to demonstrate that Lotus does not require the same hierarchical<br />

naming as an LDAP server, we created a new LDAP structure (that is, OUs) for<br />

this new LDAP server. Figure 14-22 shows that corporate users will continue to<br />

connect directly to the Lotus servers but will be authenticated via the LDAP<br />

directory. Also, Internet users will continue to access the Lotus Domino server<br />

via the reverse proxy, but will also be authenticated by the internal severs via the<br />

LDAP directory.<br />

Figure 14-22 LDAP authentication

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

Saved successfully!

Ooh no, something went wrong!