389-ds-base

#50477 COS plugin schema check does not allow attribute in extensibleobject entry
Closed: wontfix by spichugi. Opened by tbordaz.

Closed: wontfix
Reopen Issue

Issue Description

When a COS attribute is added to an entry, it first checks that the resulting entry conform the schema.
If the attribute is not allowed COS does not add the attribute.
However if the entry is extensibleobject, the checking should succeeds

Package Version and Platform

All version

Steps to reproduce

  1. Create an extensibleobject entry
  2. Create a cos that add an attribute not specify by any objectclass of the entry
  3. Search of the operational attributes. the cos attribute is not present
    3.

Actual results

cos attribute not present

Expected results

cos attribute should be present

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.2)

Metadata Update from @mreynolds:
- Issue tagged with: Schema

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/3534

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None

Schema

None
None
High
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.