22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

14.1 Basic internal collaboration (Domino, Sametime,<br />

and QuickPlace)<br />

594 Lotus Security Handbook<br />

In the first phase of our scenario, existing Lotus Domino, Sametime, and<br />

QuickPlace environments were configured for SSO functionality. Figure 14-1<br />

shows the user login path in this initial phase. Basically, a Web user connects<br />

directly to any of the Lotus servers, and is authenticated by the Domino directory.<br />

The Lotus Domino server is running LDAP and the Lotus Sametime server is<br />

connecting to the Domino server via LDAP.<br />

Figure 14-1 SSO Implementation<br />

14.1.1 Installation of the core servers<br />

The base Lotus Domino server was installed and set up as follows:<br />

► The Linux RedHat 8 Operating System was installed. The sendmail service<br />

was disabled, and the telnet and vncserver services where enabled. This<br />

allowed us to access the machine remotely and is not required for Lotus<br />

Domino installation.<br />

► Lotus Domino 6.01 was installed.<br />

► The organization was defined as <strong>Redbooks</strong>, and a new OU was created for<br />

the servers, called Servers. The servers name is<br />

itsosec-dom/Servers/<strong>Redbooks</strong>.<br />

► Two server IDs were created for the Sametime and QuickPlace servers.<br />

These servers were named itsosec-st/Servers/<strong>Redbooks</strong> and<br />

itsosec-qp/Servers/<strong>Redbooks</strong> respectively.<br />

► Two Organizational Units (OU), East and West, were created.

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

Saved successfully!

Ooh no, something went wrong!