Microsoft pumping up directory for Web use
|
|
|||
|
|
REDMOND, WASH. - The next version of Microsoft's Active Directory will include new features that begin to position the directory for use on the Web, but observers say the additions are only the first steps on a difficult path.
Microsoft bills the move as a major advancement for Active Directory, which today is geared for use within organizations as an internal network operating system directory. Microsoft wants to extend the directory's role to include managing users who are outside of an organization's firewall, such as, e-commerce customers and other Web site visitors.
Forum: Web-enabled Active Directory
Can Microsoft pull it off? Jump into the discussion.
First Microsoft must break down barriers that include Active Directory's proprietary interfaces, which hamper effective integration with the open environment of the Internet.
"On the Web, you want an independent directory server that isn't bound to NOS file and print or security. You want it more generic," says Jamie Lewis, president of The Burton Group. "Now Active Directory assumes users are [Windows 2000] NOS users, and in theory you could grant NOS privileges to users who are only Internet users."
Microsoft will head in that direction by adding two Lightweight Directory Access Protocol (LDAP) enhancements in Windows 2002 Server, formerly code-named Whistler. Microsoft has worked with Netegrity, Oblix, OpenNetwork Technologies and Securant Technologies, vendors of Web-based provisioning and access control software, on integrating Active Directory. The Windows 2002 enhancements include a performance boost in handling LDAP authentication requests and support for inetOrgPerson, a standard way to represent a user in the directory.
Microsoft wants to create the option to face the directory outward toward the Internet so it becomes a pivotal point in supporting access from outside the firewall to Web applications such as those for e-commerce and .Net, Microsoft's vision of software on the Internet.
The benefit for IT executives committed to Active Directory is the ability to create a consistent layer of directory-based user management across the internal and external portions of their networks. The directory can also support a virtual single sign-on and centralized management point to Web applications running on any platform.
Competitors have already moved their directories to the Web.
IPlanet's Directory Server, an open, general-purpose LDAP directory, now dominates that market. Novell also has moved its eDirectory onto the Web. The hallmarks of those directories are performance, scalability, standard interfaces and operating system independence.
But Microsoft isn't committing to a stand-alone directory.
"I don't think that a stand-alone directory is a firm customer requirement," says Peter Houston, group program manager for Active Directory. "But that doesn't mean we won't make it increasingly easier to deploy [Active Directory] in this [outward-facing] role."
Microsoft is hungry
Observers say for Active Directory to be in that class it needs more LDAP interfaces so applications are not tied to Microsoft's proprietary Active Directory Service Interfaces (ADSI)."Microsoft is hungry for this extranet market," says John Enck, an analyst with Gartner Group. "They are not getting the application support iPlanet is getting. These Whistler additions are good, but Microsoft still has some more concessions to make to attract applications to the [Active Directory] environment. They can't go after the Web while still mandating the use of proprietary ADSI."
Microsoft's focus now is to use LDAP to more closely integrate Active Directory with Web-based provisioning and access control software. Those products provide an HTTP interface to Web clients into a security layer for internal Web applications using policies and access controls that are stored in a directory. The products also support iPlanet and Novell directories, and some ship with iPlanet Directory Server.
Microsoft is responding to competition, but also to customers who want to simplify their directory infrastructure.
"For our business-to-business relationships we use iPlanet, but our hope is to move Active Directory out there, get off iPlanet, and get a consistent structure both internal and external," says a systems analyst for a large multinational oil and gas company who asked not to be identified.
"It would be nice to get [Active Directory] mature enough to handle that, but we don't think these new features will be all that we need," he says.
Key enhancements
The customer says his company hopes to integrate Active Directory with Netegrity's SiteMinder, which is its strategic platform for Web-access control. "We've found that when you want to tie Active Directory into these non-Microsoft components, it can get squirrely," he says.Microsoft officials say they are beginning to fix those issues with two key enhancements to Active Directory in Windows 2002 - scheduled for release early next year.
In addition to support for inetOrgPerson, Microsoft has added a feature called Concurrent Bind that hikes the performance of LDAP communication between Active Directory and access control software such as Netegrity.
Microsoft is imitating features iPlanet has used for years. The features also are part of Novell's eDirectory.
Concurrent Bind creates an open LDAP channel for exchanging authentication requests between the directory and access control software, which Microsoft refers to as a portal gateway. Typically, LDAP will open and close a channel for each request, a process that becomes time-consuming on the Web.
"With [Active Directory] we can handle several hundred authentication requests per second, but Concurrent Bind increases that by a factor of three to five," Microsoft's Houston says.
InetOrgPerson defines a standard object class with such attributes as name, e-mail address, phone and language preference. Application developers can code that standard into their software without having to create a redundant mechanism for Active Directory.
"The [Active Directory] default is that when you create a user, it's a Windows 2000 user," says Bob Worner, vice president of product engineering for OpenNetwork Technologies. "Now you can create users so they are not internal Windows 2000 users."
It's one of many enhancements that Microsoft needs to make.
"[Active Directory] is still a NOS directory that is lacking on the Internet side," says Nand Mulchandani, CTO for Oblix. "The features they are adding are a step in the right direction, but they alone won't kill iPlanet."
Mulchandani says there still is a need for more flexibility in adding, modifying and deleting schema, which defines the structure of the directory.
"We support any schema you want to load up. We don't mandate the schema like Active Directory," says David McNeely, director of product development for iPlanet.
"They are going to face some of the same challenges we did - their close ties to proprietary interfaces, access to directory services not currently available through LDAP and scalability," says Justin Taylor, chief directory strategist at Novell. "Also, we spent a lot of time making the directory modular and very friendly to other platforms."
Novell's eDirectory runs on Linux, Unix, NetWare and Windows NT and 2000, while Active Directory runs only on Win 2000.
Related Links
Contact Senior Editor John Fontana
Other recent articles by Fontana
Fill that toolbox before tackling Active Directory
Windows 2000: Lots of third-party tools are available for migrating to Active Directory. Network World, 03/29/01.
Active Directory research page
More resources.
Active Directory: How it works
Microsoft paper.
Directory standards see renewed vendor action
Novell, Microsoft propose XML-based plans. Network World, 4/2/01.
Reaction: Here's what some Fusion users are saying about this article: What do you think? Add your comments to the thread
Network World on Directories
Sign up for our free e-mail newsletter.
Breaking Active Directory news
