Hello Ulrich, I’ve to correct the information I gave at start of the tread. After investigation and some corrections on the 2MMR env, both environment gave me same result now.
In fact, I’ve proxy configuration on this replication user which works fine for a normal user that add entries in the DB, creatosname is its name, but when I use the rootdn user, it’s the replication user is stored in creatorsname. I’ve added another rule authzTo rule in the replication user for the rootdn user but it doesn’t help to get entries created by him with his name in creatorsname attribut. Brgds, Jean-Luc On 9 Mar 2022, at 09:33, Ulrich Windl <[email protected]> wrote: >>>> <[email protected]> schrieb am 08.03.2022 um 17:43 in Nachricht > <[email protected]>: >> Dears, >> >> I've a tricky issue with this attribute. >> I context of 4 MMR & 4 replicas, I've defined a rootdn and a replication >> user. When I create "ADD" a new entry in my DB with rootdn as user, the >> creatorsname is filled up with the replication username instead of rootdn >> one >> :-| > > Are you sure your replication user can read all attributes? > >> I've another configuration with 2 MMR & 2 replicas, normally same config as >> above, but there, the ADD is correctly managed. >> In both configuration, replicas send their ADD request to masters VIP with >> olcUpdateRef attribut. and received update via masters VIP with olcSyncrepl >> attribut. >> >> Any idea of any parameter, acl, schema to check ? >> >> Thx, >> J-L. > > > >
