Am 08.03.21 um 19:08 schrieb Michael Ströder:
>> Am 02.03.21 um 13:19 schrieb A. Schulze:
>>> Q: does it make sense to enforce schema checking on a LDAP consumer, too?
> Maybe it's easier to answer if you explain which problem you want to solve?
Hi Michael,
thanks to Quanah I've to clarify first: I'm not using cn=config.
my initial situation was a well running setup "single provider, multiple
consumer"
At one point in time, there is a request to extend the schema: add new
attribute types, extend existing objectClasses
Even with automation it takes time to activate the new schema on multiple
consumer:
- planing changes
- getting change dates
- get systems offline, update, check
- get systems online again
After that is done, the new scheme could be activated at the provider and new
data could be added.
So my question is more: could I avoid updating multiple consumer to save time
and effort
and get requests for schema updates done faster.
Andreas
