LDAP-UX Client Services 4.0 with Windows Server 2003 R2 Schema Support Release Notes

Table 1 Cross Reference Table Between R2's RFC2307 and SFU Schema (continued)
msSFU30memberNisNetgroupmemberNisNetgroup
msSFU30NetgroupTriplenisNetgroupTriple
msSFU30IpServicePortipServicePort
msSFU30IpServiceProtocolipServiceProtocol
msSFU30IpProtocolNumberipProtocolNumber
msSFU30OncRpcNumberoncRpcNumber
msSFU30IpHostNumberipHostNumber
msSFU30IpNetworkNumberipNetworkNumber
msSFU30IpNetmaskNumberipNetmaskNumber
msSFU30MacAddressmacAddress
msSFU30BootParameterbootParameter
msSFU30BootFilebootFile
msSFU30NisMapNamenisMapName
NOTE: In the R2' s RFC2307 schema, Microsoft introduces other UNIX attributes such as “uid” and
“unixUserPassword” to better define ADS entries with the “posixAccount” object class. Since these
UNIX attributes are not defined in IETF RFC 2307, they are not covered in table 1.
Examples
In this section, we use the “passwd” service as an example to describe the changes between the SFU3.0/3.5
and R2's RFC2307 schema.
In the current LDAP-UX Client Services 4.0 release, the following shows the attribute mappings and search
descriptor for the “passwd” service in the DUA profile required to support the SFU3.0/3.5 schema:
attributeMap: passwd:gecos=msSFU30Gecos
attributeMap: passwd:homedirectory=msSFU30HomeDirectory
attributeMap: passwd:userpassword=*NULL*
attributeMap: passwd:loginshell=msSFU30LoginShell
attributeMap: passwd:gidnumber=msSFU30GidNumber
attributeMap: passwd:uidnumber=msSFU30UidNumber
attributeMap: passwd:uid=msSFU30Name
serviceSearchDescriptor: passwd:SEARCHBASE?sub?(&(objectclass=user)
(msSFU30UidNumber=*))
In order to support the R2’s RFC2307 schema, the attribute mappings for the “passwd” service must be
re-configured and the search descriptor must be modified. The result of changes is shown below:
attributeMap: passwd:homedirectory=unixHomeDirectory
attributeMap: passwd:userpassword=*NULL*
serviceSearchDescriptor: passwd:SEARCHBASE?sub?(&(objectclass=user)(uidNumber=*))
The attribute mapping is significantly simplified because the R2’s RFC2307 schema is compliant with the
IETF RFC2307 standard. Many of the attribute mappings are no longer necessary. For example, the attribute
uidnumber is now mapped to uidNumber in the R2’s RFC2307 schema. Since the attribute names are
the same, the attribute mapping for uidnumber is not necessary.
Cross Reference Table 9