LDIF Examples

These examples show the objectclasses and attributes that are typically used for the standard solaris data files.
Not all the supplied attributes are mandatory - check the schema to find out which are mandatory and those that are optional.

Password LDIF example

dn: cn=jw,ou=people,dc=ldap,dc=net
changetype: add
objectclass: account
objectclass: posixAccount
objectclass: shadowAccount
cn:jw
uid:jw
uidNumber: 10000
gidNumber: 1000
gecos: JW
homeDirectory:  /home/jw
loginShell: /bin/ksh
userPassword: {crypt}zzzzzzxxxxxx
shadowLastChange:10000
Group LDIF example

dn: cn=sa,ou=group,dc=ldap,dc=net
changetype: add
objectClass: posixGroup
objectClass: top
cn: sa
gidNumber: 1000
memberUid: jw
memberUid: sw
Hosts LDIF example

Normally DNS will be used for hostnames so this container will not be populated
dn: cn=caracas+ipHostNumber=1.2.3.4,ou=Hosts,dc=ldap,dc=net
objectClass: ipHost
objectClass: device
objectClass: top
cn: caracas
cn: loghost
ipHostNumber: 1.2.3.4
Services LDIF example

dn: cn=chargen+ipServiceProtocol=udp,ou=services,dc=ldap,dc=net
objectClass: ipService
objectClass: top
cn: chargen
cn: ttytst
cn: source
ipServicePort: 19
ipServiceProtocol: udp
RPC LDIF example

dn: cn=rpcbind,ou=rpc,dc=ldap,dc=net
objectClass: oncRpc
objectClass: top
cn: rpcbind
cn: portmap
cn: sunrpc
oncRpcNumber: 100000
Protocols LDIF example

dn: cn=icmp,ou=protocols,dc=ldap,dc=net
objectClass: ipProtocol
objectClass: top
cn: icmp
ipProtocolNumber: 1
Ethers and Bootparams LDIF example

Note that the ethers and bootparams data share the same container, ou=ethers and they just use different attributes. The first LDIF example here is for a ethers entry and the second is for a bootparams entry.

Ethers entry
dn: cn=mars,ou=ethers,dc=ldap,dc=net
objectClass: ieee802Device
objectClass: top
cn: mars
macAddress: 8:0:20:11:22:33

Bootparams entry
dn: cn=caracas,ou=ethers,dc=ldap,dc=net
objectClass: bootableDevice
objectClass: top
cn: caracas
bootParameter: caracas
bootParameter: root=bootsrv:/opt/Jumpstart/Solaris9/config//../Solaris_9/Tools/Boot
bootParameter: install=instsrv:/opt/Jumpstart/Solaris_9
bootParameter: boottype=:in
bootParameter: sysid_config=instsrv:/opt/Jumstart/Solaris9/config/
bootParameter: install_config=instsrv:/opt/Jumpstart/Solaris_9/config/
bootParameter: rootopts=:rsize=32768
bootParameter: ns=1.2.3.4:nisplus(255.255.255.0)
bootParameter: domain=dns.com
Netgroups LDIF example

dn: cn=eng,ou=netgroup,dc=ldap,dc=net
objectClass: nisNetgroup
objectClass: top
cn: eng
nisNetgroupTriple: (,jw,)
nisNetgroupTriple: (,sw,)
nisNetgroupTriple: (,gs,)
Networks and Netmasks LDIF examples

Note that the networks and netmasks data share the same container, ou=networks and they just use different attributes. The first LDIF example here is for a networks entry and the second is for a netmasks entry.

Networks entry

dn: ipNetworkNumber=10.0.0.0,ou=networks,dc=ldap,dc=net
objectClass: ipNetwork
objectClass: top
cn: arpanet
cn: arpa
ipNetworkNumber: 10.0.0.0

Netmasks entry
dn: ipNetworkNumber=1.2.3.0,ou=networks,dc=ldap,dc=net
objectClass: ipNetwork
objectClass: top
ipNetworkNumber: 1.2.3.0
ipNetmaskNumber: 255.255.255.0
Printers LDIF example

Note: The print clients setup is implemented with lpset not ldapaddent

eg.

lpset -n ldap -h saturn -D "cn=Directory Manager" -w secret -a bsdaddr=mars.dns.com,printer1,Solaris printer1

This generates the following entry in the directory server:
dn: printer-uri=printer1,ou=printers,dc=ldap,dc=net
objectClass: top
objectClass: printerService
objectClass: printerAbstract
objectClass: sunPrinter
printer-name: printer1
sun-printer-bsdaddr: mars.dns.com,printer1,Solaris
printer-uri: printer1
Automount map LDIF example

(Auto_home in this case)
dn: automountKey=jw,automountMapName=auto_home,dc=ldap,dc=net
objectClass: automount
objectClass: top
automountKey: jw
automountInformation: homesrv:/export/home/jw