Kurt Zeilenga wrote:
One additional note, I generally would advise that a schema-aware client not alter it's update behavior of elements based upon whether said elements are active or inactive (OBSOLETE) in the schema.
I disagree especially for cases when new data is added.
Instead, they should just try the update and, if it fails, report it as they normally would.
Modifying existing data I first have to think about...
Handling the inactive condition locally hides the error from the directory administrator, who is likely relying on directory server logs to find applications which using inactive schema.
Hmm, that's not the case with a schema-aware client anyway which guides the user *not* to use OBSOLETE schema elements. You're likely talking about detecting pre-configured applications with hard-coded use of OBSOLETE object classes and attribute types. Most times these are not schema-aware at all.
Ciao, Michael.