https://bugs.openldap.org/show_bug.cgi?id=8149
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
Added forwarding option in
https://git.openldap.org/openldap/openldap/-/merge_requests/931
We can't really make loginStatus operational since it's loaded from
ldapns.schema. I mean, to do so requires hardcoding it into nssov's code.
Which we could do, certainly. But it'll cause some confusion for existing
configs, as we already saw when hardcoding ppolicy schema.
The issue with opattrs / MMR replication needs some more thought. I've left it
for now but perhaps we should just let it be treated as a completely ordinary
mod.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8884
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|CONFIRMED |RESOLVED
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
Fixed in git 2b8cbe0aace6d7eea7a8b93a90afdbb94b81a0a9
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8884
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
Perhaps the code in rwm assumed the frontend would attach entryDN after the
overlays transformations were completed. But clearly that's not what happens.
--
You are receiving this mail because:
You are on the CC list for the issue.