The schema replication protocol is incorrectly adding 'user defined' to standard schema attributes and objectclasses. This results in the "standard" schema being able to be updated - when its supposed to remain read-only.
Metadata Update from @mreynolds: - Custom field type adjusted to defect - Issue set to the milestone: 1.3.7.0
Could be a duplicate of https://pagure.io/389-ds-base/issue/47749
Metadata Update from @tbordaz: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue close_status updated to: duplicate - 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/2274
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: duplicate)
Login to comment on this ticket.