Rich Megginson wrote: > Unfortunately, the objectclass "account" is a structural objectclass, > which means you can't "mix it in" with other structural objectclasses > such as inetOrgPerson. So I think either the standard needs to be > revised to make account auxiliary, or create a new objectclass > (auxAccount?). What keeps you from doing this (I ask because I've mixed these before, and nothing "bad" happened)? Where is that restriction defined? (I feel kinda stupid if I've been doing this for all these years and in all that time it hasn't been "allowed" :) ) - Jeff
