[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Auxiliary object class practically of no use?
- To: openldap-technical@openldap.org
- Subject: Auxiliary object class practically of no use?
- From: dE <de.techno@gmail.com>
- Date: Wed, 15 Apr 2015 09:02:00 +0530
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=0rwUD0IXgLuzbeAocjoHzv5G9yJ/0YHtq8cwcYsGeLM=; b=ZrTcUwQLsHI7sW9GmItUX/mE+biUx9mzDnxy8MUL9gphUJOV6sCox/soKmBhJvGmio VHiI4y+VXtFaJfrZVcrsmZHoN+6K16oVHH2AwDFb+dfpNWN8by72q2Ecouxe/GDJ9oUb nMvDp1RSLBhlGrDRPSyiqnnXm+eMNv9HGsOCrop8MtRDqXlDyZjWOOS5mVRBRuKhe+eM iNDJYXu+7UQj9rDp8YatzaAWcn0Z2CfxJ6veYIn32WUoIcuDC2zQPGUV5vnn0abn+Cp/ ER4IaOidEyekPkaDbg/TFccSjLkmj8QSDC/ev5ZZKvLlVDd7JKe5eNGUM+64BCwT1Vkm wz8A==
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
According to RFC 4512
An entry can belong to any subset of the set of auxiliary object
classes allowed by the DIT content rule associated with the
structural object class of the entry.
From what I understand, this means auxiliary classes do not 'augment';
the no. of attributes which are possible in an entry must be a subset of
the structural object class the entry belongs to.