we actually did(fix!) this intentionally in the recent release to prevent a user from deleting these attributes. This also helps in letting the users know what attributes are there that are mandatory for the server to function and their default values.
On Wed, Dec 26, 2012 at 4:01 PM, Emmanuel Lécharny <[email protected]>wrote: > Hi ! > > as I'm writing the doc about configuration, I'm wondering if some of the > MUST attributeType we have in many of the configuration ObjectClasses > should not be MAY attributeTypes instead. For instance, considering the > ads-directoryService ObectClass, we have : > > m-must: ads-directoryServiceId > m-must: ads-dsReplicaId > m-must: ads-dsAccessControlEnabled > m-must: ads-dsAllowAnonymousAccess > m-must: ads-dsDenormalizeOpAttrsEnabled > m-must: ads-dsPasswordHidden > m-must: ads-dsSyncPeriodMillis > m-may: ads-dsTestEntries > > Many of those AttributeType have default values, and we probably don't > need to require the administrator to fill some value for, say, > ads-dsSyncPeriodMillis. > > I would rather suggest we switch from MUST to MAY some of the > AttributeType, something like : > > > m-must: ads-directoryServiceId > m-must: ads-dsReplicaId > m-may: ads-dsAccessControlEnabled > m-may: ads-dsAllowAnonymousAccess > m-may: ads-dsDenormalizeOpAttrsEnabled > m-may: ads-dsPasswordHidden > m-may: ads-dsSyncPeriodMillis > m-may: ads-dsTestEntries > > Such a modification could be done for other ObjectClasses. > > wdyt ? > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > > -- Kiran Ayyagari http://keydap.com
