[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema

To: Michael Ströder <michael@stroeder.com>, openldap-technical@openldap.org
Subject: Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
From: Howard Chu <hyc@symas.com>
Date: Mon, 6 Nov 2017 14:05:02 +0000
In-reply-to: <5dd30907-ba28-6ff5-749d-c5d64f6317e9@symas.com>
References: <f97650ff-7df0-25da-3c10-da87c0346a28@stroeder.com> <WM!d41b198aeb01c38dfdc580abcee524fddde798284e91017238c6e65eada8e47f2a182b6b5900d706e888531f4f247e83!@mailstronghold-1.zmailcloud.com> <5dd30907-ba28-6ff5-749d-c5d64f6317e9@symas.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53a1

Howard Chu wrote:

Michael Ströder wrote:
HI!

Why is it not allowed to use

   NO-USER-MODIFICATION
   USAGE dSAOperation

in an attribute type declaration?
Because such an operational attribute requires server-side code to actuallyimplement it, and you haven't got any means to provide that code. Customoperational attributes must be defined using code loaded in a module.


You could use the dsaschema contrib module to help with this.



--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Follow-Ups:
- Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
  - From: Michael Ströder <michael@stroeder.com>

References:
- NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
  - From: Michael Ströder <michael@stroeder.com>
- Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
Next by Date: Re: NO-USER-MODIFICATION and USAGE dSAOperation in custom schema
Index(es):
- Chronological
- Thread