"A. Schulze" sca@andreasschulze.de schrieb am 08.03.2021 um 23:04 in
Nachricht ad89bcd6-33bd-623c-51a6-28e844bd3b8e@andreasschulze.de:
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.
I think it mostly depends on the "type of schema update": If the update is compatible with existing data, it's easy, if the data needs adjustment you'll have the problem: What to update first? Data or schema? In both cases the data will look inconsistent.
Andreas