Issue 5714 - [feature request] operational attrs defined via configuration
Summary: [feature request] operational attrs defined via configuration
Status: VERIFIED WONTFIX
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- enhancement
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-27 19:48 UTC by ando@openldap.org
Modified: 2023-10-09 17:14 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ando@openldap.org 2008-09-27 19:48:57 UTC
Full_Name: Pierangelo Masarati
Version: HEAD
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (151.30.78.88)


Currently, the attributeType statement does not allow to define operational
attributes.  The rationale was that operational attributes are somehow
application-maintained, so configuration-defined attrs would be essentially
unmaintainable.  At the same time, modules that are able to maintain operational
attributes can register them bypassing some of the checks attributes defined via
configuration must pass.  However, the availability of the "relax" control could
make this restriction too strict.  In fact, there are works in progress (e.g.
draft-wahl-ldap-adminaddr) that define operational attrs which could easily be
defined via configuration and maintained via the relax control.  This is a
feature request to suggest the possibility to define operational attrs via
configuration.

p.

Comment 1 ando@openldap.org 2008-09-28 18:56:10 UTC
moved from Incoming to Software Enhancements
Comment 2 Quanah Gibson-Mount 2023-10-09 17:14:45 UTC
dsaschema contrib module handles this already.