https://bugzilla.redhat.com/show_bug.cgi?id=668808
Description of problem: When implementing CoS for an attribute that includes a language code (RFC2596), it's value is NOT returned during searching. When implementing CoS for the same attribute without a language code (RFC2596), the value is returned. How reproducible: Always. Steps to Reproduce: Set up a simple CoS and a CoS template. dn: cn=CIKO CoS,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg cosAttribute: ou;lang-bg cosAttribute: ou costemplatedn: cn=CIKO Template, cn=CIKO CoS, ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg objectClass: top objectClass: ldapsubentry objectClass: cossuperdefinition objectClass: cosPointerDefinition cn: CIKO CoS dn: cn=CIKO Template,cn=CIKO CoS,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg cn: CIKO Template cosPriority: 1 ou;lang-bg:: 0KbQmNCa0J4= objectClass: top objectClass: costemplate objectClass: extensibleobject Do an ldapsearch on an object, that should inherit the CoS definition. # ldapsearch -x uid=dstoykov ou -LLL Actual results: dn: uid=dstoykov,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg ou: CIKO Expected results: dn: uid=dstoykov,ou=CIKO,ou=People,dc=ru,dc=acad,dc=bg ou: CIKO ou;lang-bg:: 0KbQmNCa0J4=
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @nkinder: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from Needs Review) - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.6 backlog)
Reopen is someone needs this...
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/69
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.
Login to comment on this ticket.