ldapmodify ... dn: cn=cos-definition,dc=example,dc=com changetype: add objectClass: cosIndirectDefinition objectClass: cosSuperDefinition objectClass: top objectClass: ldapSubEntry cosIndirectSpecifier: manager cosAttribute: roomnumber
ldapsearch ... -b "dc=example,dc=com" uid=user.9990 roomnumber manager dn: uid=user.9990,ou=People,dc=example,dc=com
ldapsearch ... -b "dc=example,dc=com" uid=user.9992 roomnumber manager dn: uid=user.9992,ou=People,dc=example,dc=com
ldapmodify ... dn: uid=user.9990,ou=People,dc=example,dc=com changetype: modify add: roomnumber roomnumber: 99
dapsearch -b "dc=example,dc=com" uid=user.9992 roomnumber manager dn: uid=user.9992,ou=People,dc=example,dc=com
ldapmodify ... dn: uid=user.9992,ou=People,dc=example,dc=com changetype: modify add: manager manager: uid=user.9990,ou=People,dc=example,dc=com
ldapsearch ... -b "dc=example,dc=com" uid=user.9992 roomnumber manager dn: uid=user.9992,ou=People,dc=example,dc=com roomnumber: 99 manager: uid=user.9990,ou=People,dc=example,dc=com
ldapmodify ... dn: uid=user.9990,ou=People,dc=example,dc=com changetype: modify replace: roomnumber roomnumber: 777
ldapsearch ... -b "dc=example,dc=com" uid=user.9992 roomnumber manager dn: uid=user.9992,ou=People,dc=example,dc=com roomnumber: 777 manager: uid=user.9990,ou=People,dc=example,dc=co
I think the cos is evaluated when the entry is loaded to the entry cache and changes in th etemplate are not recognized
Wonder if this bug a side effect of https://fedorahosted.org/389/ticket/512, that may cache values returned from a Service Provider (here cos). For indirect cos, caching is possible a bad option.
might be a duplicate of 47715.
no clone, can be covered by upstream test
attachment 0001-Ticket-47921-indirect-cos-does-not-reflect-changes-i.patch
b0213c1..bff826b master -> master commit bff826b Author: Mark Reynolds mreynolds@redhat.com Date: Thu Jun 11 12:28:07 2015 -0400
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.0
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1252
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.