Microsoft has released
Active Directory Service Interfaces (ADSI)
for Windows9x, NT and Windows 2000, and now it's inbuilt in Windows 2000. The Windows2000 application specification states that you must use Active Directory when youcan, so now you're thinking: How are
applications going to adapt? Whatchanges do you need to make? How are you going to use Delphi effectively to makethese changes? This is what I intend to address in this presentation.Let me first introduce a
. A directory service is like atelephone directory: if you have aperson’s name, you can find his/herphone number. A directory servicekeeps track of “resources”, which couldbe anything – a file system is adirectory that keeps track of files andfolders, an email server is a directoryservice that indexes users, user groupsetc. There are many directory servicesalready in place: we already have filesystems and email servers. What’s sodifferent? Traditionally, you’d have touse
different API’s (ApplicationProgramming Interfaces)
to accessdifferent directory services – which :
Limit you to the vendor’sdirectory service
. For example, if youwrote an application that extractedemail information from Microsoft Mailand used the Mail ApplicationProgrammers Interface (MAPI), youwould find it difficult to move to adifferent vendor.
Increase development time for your applications
because you needto learn more API’s to get yourapplication working.There is a need to have a
that every directory servicewould support – similar to the ODBCprogramming model that all (or most)database vendors now support. Amodel that will support a
of resources, like folders and files, and besimple to use.
provides this model. To access anActive Directory, you will use
ActiveDirectory Service Interfaces