There is an attribute that controls what object classes to apply to the user object. The framework should go beyond just applying the classes listed there. If this value changes or at the start of the httpd the object classes listed there should be checked against the schema and the attributes managed by those classes should be automatically added to the list of the attributes that can be enabled for management via UI and CLI. This list can be stored in a different attribute. This would allow to just drop user extension schema and enable attributes that this schema brings in the UI CLI. That would be a huge simplification of the way how the deployments can extend our schema for specific use. In addition to enablement there might be some other metadata that needs to be saved together with the enablement: label in UI, default value, name of the CLI parameter if different from the attribute name, etc. May be JSON should be used to describe each item and be stored in a MV config attribute.