28 May
2021
28 May
'21
3:20 p.m.
https://bugs.openldap.org/show_bug.cgi?id=9295
--- Comment #9 from Michael Ströder michael@stroeder.com --- (In reply to Ondřej Kuzník from comment #5)
The way we munge the inbound op can backfire on operations like this:
add: singlevalued singlevalued: new - delete: singlevalued singlevalued: oldArguably, applications that do this are strange, but the protocol allows this and it's accepted on the provider.
Note that it's not strange at all: This is the recommended client behaviour when using an ID pool entry for unique ID assignment.
I'm glad this will be fixed in 2.4.59.
--
You are receiving this mail because:
You are on the CC list for the issue.