ConfigurationMaps-RFC2307

Configuration Maps for RFC2307

DBIS provides an improved schema that is an evolution of RFC2307 and which adds many improvements. These are described in its own set of IETF internet drafts. To set-up configuration maps using the improved DBIS schema, see [Configuration Maps]. If, however, you are using the old RFC2307 schema already in your LDAP directory, and you are not in a position to migrate to the new schema, you can still use DBIS and will need to configure the DBIS configuration maps so that it understands that schema.

Note that a database can contain entries obtained via multiple configuration maps, so it is possible to have some entries defined the old way, while defining new entries the new way, and still maintaining single coherent maps that can be used by clients.

This page provides example configuration map entries for each of the databases supported by RFC2307.

The netgroup database

The dbisNetgroupConfig entries will need to filter on the nisNetgroup class, and remap the cn, nisNetgroupTriple and memberNisNetgroup attributes. Note that there should be two entries for nisNetgroupTriple, one to remap the user component and one to remap the host and domain components:

dn: cn=netgroup-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisNetgroupConfig
cn: netgroup-legacy
dbisMapDN: ou=netgroup,ou=sales,o=infra
dbisMapFilter: objectClass=nisNetgroup
dbisMapClass: netgroupObject=nisNetgroup
dbisMapAttr: en=cn
dbisMapAttr: netgroupUser=nisNetgroupTriple
dbisMapAttr: netgroupHost=nisNetgroupTriple
dbisMapAttr: exactNetgroup=memberNisNetgroup
description: netgroup database entries that use the legacy RFC2307 schema

The passwd database

The dbisPasswdConfig entries will need to filter on the posixAccount class, and remap the uid attribute. The dbisMapGecos attribute can map directly to the gecos attribute:

dn: cn=passwd-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisPasswdConfig
cn: passwd-legacy
dbisMapDN: ou=passwd,ou=sales,o=infra
dbisMapFilter: objectClass=posixAccount
dbisMapClass: posixUserAccount=posixAccount
dbisMapAttr: en=uid
dbisMapGecos: gecos
description: passwd database entries that use the legacy RFC2307 schema

The group database

The dbisGroupConfig entries will need to filter on the posixGroup class, and remap the cn and memberUid attributes:

dn: cn=group-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisGroupConfig
cn: group-legacy
dbisMapDN: ou=group,ou=sales,o=infra
dbisMapFilter: objectClass=posixGroup
dbisMapClass: posixGroupAccount=posixGroup
dbisMapAttr: en=cn
dbisMapAttr: exactUser=memberUid
description: group database entries that use the legacy RFC2307 schema

The hosts database

The dbisHostConfig entries will need to filter on the ipHost class, remap the ipHost class and remap the cn and ipHostNumber attributes:

dn: cn=hosts-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisHostConfig
cn: hosts-legacy
dbisMapDN: ou=hosts,ou=sales,o=infra
dbisMapFilter: objectClass=ipHost
dbisMapClass: ipHostObject=ipHost
dbisMapClass: ipv4HostObject=ipHost
dbisMapClass: ipv6HostObject=ipHost
dbisMapAttr: rn=cn
dbisMapAttr: ipv4Address=ipHostNumber
dbisMapAttr: ipv6Address=ipHostNumber
description: hosts database entries that use the legacy RFC2307 schema

With the above remapping rules, IPv4 and IPv6 addresses will be handled correctly and mapped to their respective DBIS classes and attributes.

The ethers database

DBIS makes no changes to the way that ethers database entries are defined:

dn: cn=ethers-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisEtherConfig
cn: ethers-legacy
dbisMapDN: ou=hosts,ou=sales,o=infra
dbisMapFilter: objectClass=ieee802Device
dbisMapAttr: rn=cn
description: ethers database entries that use the legacy RFC2307 schema

The bootparams database

DBIS makes no changes to the way that bootparams database entries are defined:

dn: cn=bootparams-legacy,ou=rfc2307,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisBootConfig
cn: bootparams-legacy
dbisMapDN: ou=hosts,ou=sales,o=infra
dbisMapFilter: objectClass=bootableDevice
dbisMapAttr: rn=cn
description: bootparams database entries that use the legacy RFC2307 schema

The networks database

The dbisNetworkConfig entries will need to filter on the ipNetwork class, remap the ipNetwork class and remap the cn attribute:

dn: cn=networks-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisNetworkConfig
cn: networks-legacy
dbisMapDN: ou=networks,ou=sales,o=infra
dbisMapFilter: objectClass=ipNetwork
dbisMapClass: ipNetworkObject=ipNetwork
dbisMapAttr: en=cn
description: networks database entries that use the legacy RFC2307 schema

The services database

The dbisServiceConfig entries will need to filter on the ipService class, remap the ipService class and remap the cn and ipServiceProtocol attributes:

dn: cn=services-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisServiceConfig
cn: services-legacy
dbisMapDN: ou=services,ou=sales,o=infra
dbisMapFilter: objectClass=ipService
dbisMapClass: ipServiceObject=ipService
dbisMapAttr: en=cn
dbisMapAttr: ipProtocolName=ipServiceProtocol
description: services database entries that use the legacy RFC2307 schema

The protocols database

The dbisProtocolConfig entries will need to filter on the ipProtocol class, remap the ipProtocol class and remap the cn attribute:

dn: cn=protocols-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisProtocolConfig
cn: protocols-legacy
dbisMapDN: ou=protocols,ou=sales,o=infra
dbisMapFilter: objectClass=ipProtocol
dbisMapClass: ipProtocolObject=ipProtocol
dbisMapAttr: en=cn
description: protocols database entries that use the legacy RFC2307 schema

The rpc database

The dbisRpcConfig entries will need to filter on the oncRpc class, remap the oncRpc class and remap the cn and oncRpcNumber attributes:

dn: cn=rpc-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisRpcConfig
cn: rpc-legacy
dbisMapDN: ou=rpc,ou=sales,o=infra
dbisMapFilter: objectClass=oncRpc
dbisMapClass: rpcObject=oncRpc
dbisMapAttr: en=cn
dbisMapAttr: rpcNumber=oncRpcNumber
description: rpc database entries that use the legacy RFC2307 schema

Custom NIS maps

The dbisCustomConfig entries will need to filter on the nisObject class, set the customMapName attribute and remap the cn and nisMapEntry attributes:

dn: cn=nismap-legacy,en=sales.corp,ou=domain-mappings,o=infra
objectClass: top
objectClass: dbisMapConfig
objectClass: dbisCustomConfig
cn: nismap-legacy
customMapName: tracks
dbisMapDN: nisMapName=tracks,ou=sales,o=infra
dbisMapFilter: objectClass=nisObject
dbisMapAttr: en=cn
dbisMapAttr: customMapValue=nisMapEntry
description: nismap custom database entries that use the legacy RFC2307 schema

Next Steps

Return to [Configuring DBIS] for the next steps in setting up a new installation. This includes setting up advanced features such as [Remapping Rules], [Transformation Rules], [Overlays], [Netgroup Constraints] and [Netservices].