
NT4-Specific Limitations
568
Red Hat Directory Server Administrator’s Guide • May 2005
• Active Directory uses the attribute
streetAddress
for a user or group’s
physical or postal address. Directory Server uses the RFC2798 inetOrgPerson
attribute
street
for this purpose. However, as defined in RFC2256,
streetAddress
is an
alias
for
street
. To compound the confusion, Active
Directory also has the
street
attribute, but it is not an alias for
streetAddress
but a separate attribute that can hold an independent value.
Windows Sync maps
streetAddress
in Windows to
street
in Directory
Server, and therefore, precludes the use of the
street
attribute in Active
Directory.
NT4-Specific Limitations
The NT4 LDAP Service attempts to reflect the NT4 NTLM user database (as
accessed via the Net API) in LDAP. In general, this works well, but there are some
fundamental incompatibilities between LDAP schema and the underlying data
store. These incompatibilities are listed below:
• The schema supported by the NTLM database is severely limited compared
to Active Directory. There is little support for information beyond username
and full name. The missing attributes therefore cannot be synchronized.
• There is no support for the incremental Dirsync found in Active Directory.
What this means is that every time the Directory Server performs a
synchronization pass, it will pull the complete set of all entries from NT4. This
has implications for the consistency of data because if a modification is made
to an entry on the Directory Server side and the same entry is read from NT4
in a synchronization operation before the change has been propagated
outbound, then the change will be undone.
• There is no support for tombstone entries in NT4. What this means is that
entries deleted from NT4 will not be automatically deleted from the Directory
Server side. It will be necessary to delete those entries manually.
• NT4 has no
surname
attribute. However, the
inetOrgPerson
object class
requires
surname
have a value. In order to allow the use of the standard
person schema with NT4, when new user entries are created in the sync
process, they are given a
surname
attribute value that is equal to the NT user
name. This can be changed later by the admistrator to the correct value. This
issue only applies to new entries created in Directory Server by a sync
operation. If the associated Directory Server entry for an NT4 user account
already exists, its
surname
attribute is left unchanged.
Содержание DIRECTORY SERVER 7.1
Страница 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Страница 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Страница 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 278: ...Compatibility with Earlier Releases 278 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 374: ...Troubleshooting Replication Related Problems 374 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 478: ...Using the Management Information Base 478 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 545: ...About Windows Sync Chapter 18 Windows Sync 545 Figure 18 1 Active Directory Directory Server Synchronization Process ...
Страница 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 586: ...Storing Information in Multiple Languages 586 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 606: ...Searching an Internationalized Directory 606 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Страница 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...