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.

8.3.6 Event-driven synchronization<br />

8.3.7 Tools<br />

326 Lotus Security Handbook<br />

Events can be described as the circumstances dictate when one set of data<br />

sources communicates with another. One example is whenever an employee is<br />

added to, updated within, or deleted from the HR system. Another example is<br />

when the access control system detects a keycard being used in a restricted<br />

area. An event can also be based on a calendar or a clock-based timer, for<br />

example, starting communications at 12:00 midnight every day except Sunday. It<br />

might even be a one-off event, for example, populating a directory.<br />

Events are usually tied to a data source, and are related to the data flows that are<br />

triggered when the specified set of circumstances arise.<br />

There are several tools available for directory synchronization. In this section, we<br />

describe three tools that are currently available from <strong>IBM</strong> that support directory<br />

synchronization between Lotus Domino and other third-party directories.<br />

ADSync<br />

The Active Directory Synchronization tool, or ADSync, allows Active Directory<br />

administrators to manage (register, delete, and rename) users and groups in<br />

both Active Directory and the Domino Directory as a unified operation from the<br />

Active Directory Users and Computers Console.<br />

To use Lotus Active Directory Synchronization, the Domino Administration client<br />

must be installed on the same workstation used to manage users and computers<br />

within your Active Directory. ADSync, despite its name, is not actually a directory<br />

synchronization tool. It is more like an administrator client “conduit” that lets<br />

Windows administrators manage both Domino Directory and AD users from a<br />

single user interface. Domino and Windows each have their own credentials,<br />

management consoles, and directories. ADSync links the two on a single<br />

machine, so changes made to AD are pushed to Domino using an installed but<br />

essentially hidden Domino Administrator client. In other words, it performs<br />

administrator functions simultaneously, and hides the secondary changes to<br />

Domino from the administrator’s screen.<br />

ADSync is a new feature included with Domino 6. With it, you can create new<br />

users and groups in Active Directory and have those changes reflected in the<br />

Domino Directory, including the creation of person or group documents, Notes<br />

IDs, passwords, and mail files for the users. In order to accomplish these tasks,<br />

the Active Directory administrator must have a properly certified Notes ID and<br />

appropriate access to make changes in the Domino Directory. The registration<br />

server must be Domino 6 or later and the Domino Administration client must be a<br />

6 or later client. Additionally, policies must be created that contain sub policies,

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

Saved successfully!

Ooh no, something went wrong!