Factotum: Documentation Handyman

Need to know what attributes Calendar Server requires in Directory Server for an end user? The following sample for a newly created user using the commadmin user create command to create a mail/calendar user should get you there. (Hat tip Deb)

# cd /opt/SUNWcomm/bin
# ./commadmin user create -D admin -w password -F New -l nuser -L User \
-n lab.example.com -p 80 -W password -X construction.lab.example.com -S \
mail,cal -E nuser@lab.example.com -H construction.lab.example.com

# cd /opt/SUNWdsee/dsee6/bin/
# ./ldapsearch -D "cn=directory manager" -w password -b o=isp uid=nuser
version: 1
dn: uid=nuser,ou=People,o=lab.example.com,o=isp
icsFirstDay: 2
userPassword: {SSHA}RMn5bkqZRlLOI03vnmutikGAcvRgVdlvk2lGfQ==
uid: nuser
iplanet-am-modifiable-by: cn=Top-level Admin Role,o=isp
icsTimezone: America/Denver
givenName: New
mail: nuser@lab.example.com
mailUserStatus: active
sn: User
cn: New User
mailDeliveryOption: mailbox
icsStatus: Active
icsCalendar: nuser@lab.example.com
mailDeferProcessing: No
mailHost: construction.lab.example.com
objectClass: userpresenceprofile
objectClass: icscalendaruser
objectClass: top
objectClass: iplanet-am-managed-person
objectClass: iplanet-am-user-service
objectClass: organizationalperson
objectClass: inetadmin
objectClass: person
objectClass: sunamauthaccountlockout
objectClass: inetuser
objectClass: inetlocalmailrecipient
objectClass: iplanetpreferences
objectClass: ipuser
objectClass: inetorgperson
objectClass: inetsubscriber
objectClass: inetmailuser
inetUserStatus: Active

Notes:

• The icsFirstDay and icsTimeZone attributes are not absolutely required and will be created when a user first logs in. However, the others are required and if using DWP, setting icsDWPHost to the Calendar backend host may be necessary (though this should also get set upon first login).
• Also, creating users using the above commands, make sure the domain is also enabled for mail and calendar, for example:

  # ./commadmin domain modify -D admin -w password -X construction.lab.example.com -n \
  lab.example.com -p 80 -d lab.example.com -S mail,cal -H construction.lab.example.com
  

  So the domain entry in LDAP looks like:

  dn: o=lab.example.com,o=isp
  o: lab.example.com
  objectClass: inetdomainauthinfo
  objectClass: sunismanagedorganization
  objectClass: top
  objectClass: sunnamespace
  objectClass: sundelegatedorganization
  objectClass: sunmanagedorganization
  objectClass: maildomain
  objectClass: icscalendardomain
  objectClass: organization
  objectClass: nsManagedDomain
  mailAccessProxyPreAuth: no
  icsTimezone: America/Denver
  sunRegisteredServiceName: DomainMailService
  sunRegisteredServiceName: GroupMailService
  sunRegisteredServiceName: GroupCalendarService
  sunRegisteredServiceName: UserMailService
  sunRegisteredServiceName: iPlanetAMAuthService
  sunRegisteredServiceName: UserCalendarService
  sunRegisteredServiceName: iPlanetAMAuthLDAPService
  sunRegisteredServiceName: DomainCalendarService
  sunNameSpaceUniqueAttrs: uid
  mailDomainStatus: active
  preferredMailHost: construction.lab.example.com
  nsNumUsers: 1
  icsStatus: active
  icsExtendedDomainPrefs: domainaccess=@@d^a^lsfrwd^g;anonymous^a^r^g;@^a^s^g
  icsExtendedDomainPrefs: calmasterUid=calmaster
  sunPreferredDomain: lab.example.com
  inetDomainStatus: active
  sunOrgType: full
  sunNumUsers: 18