Hi, Thank you for the response. Yes, the glue value is added by replication. The issue occurs only when multi-master replication is configured. The full tree is replicated with the proper permissions, and all other entries are replicated correctly.
However, our application does not work when the objectClass value is set to glue. We want to ensure replication always includes the correct value and never results in a glue entry. To achieve this, we need to understand the scenarios where replication adds glue values and find ways to eliminate such cases. With the glue attribute value, we are unable to read the entry properly. Even if we do read the entry, the application requires the actual value instead of glue for it to function correctly.
