Hi!
I feel that when an application insists on some attribute being present, while the schema does not require it, the solution is to define that attribute for all entries, or convince the provider of the application to fix it.
I agree that there are some scenarios (e.g. ppolicy) where there are default values when an attribute is not set, and the way to handle it in an app is to "know" (it cannot be read from LDAP) the default value and to use that if the attribute's value is not set. Unfortunately when the built-in default changes, one would first have to notice that and second one would have to update the app.
Kind regards, Ulrich
-----Original Message----- From: Geert Hendrickx geert@hendrickx.be Sent: Wednesday, July 3, 2024 3:49 PM To: openldap-technical@openldap.org Subject: [EXT] dummy values for absent attributes ?
Hi
We are facing a proprietary application that insists on the presence of certain attributes that are optional in our objectclass schema, and not all objects have them.
So we are considering to provision dummy values to all objects that currently don't have these attributes, but that would impact a large number of objects, which I'd like to avoid. (And we'd also have to adjust business logic to always add those attributes in the future, whereas they are truly optional in our data model.)
Is there an OpenLDAP overlay that can insert dummy values for missing attributes? For arbitrary objects? (I read about slapo-translucent, but I think it requires each object to be present in the transcluent database?)
Geert