OpenDJ: CoS with Collective Attributes

OpenDJ Community Logo This morning found me scratching my head for a reasonable example for the OpenDJ admin guide chapter on virtual and collective attributes. I ended up adding some more content to the Example.ldif file I have been using, including some comments at the top about how to update the schema. 😦

I write 😦 not because updating directory schema is difficult… in fact its really easy with OpenDJ. 🙂 But it makes the example more complicated.

Trouble is, who wants to generate postal address or zip code based on location? Or add a manager hierarchy to the sample data? I wanted to do this:

This example positions collective attributes that depend on the classOfService attribute values.

  • For entries with classOfService: bronze, mailQuota is set to 1 GB, and diskQuota is set to 10 GB.
  • For entries with classOfService: silver, mailQuota is set to 5 GB, and diskQuota is set to 50 GB.
  • For entries with classOfService: gold, mailQuota is set to 10 GB, and diskQuota is set to 100 GB.

Collective attributes make that pretty easy as shown in the doc. But you still need to add the attributes and an object class to allow them.

Advertisements

Leave a comment

Filed under Directory Services and LDAP

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s