Comparison of attributetype schema definitions does not support aliases. For example the two definitions are equal
attributeTypes: ( 2.5.4.3 NAME ( 'cn' 'commonName' ) SUP name X-ORIGIN 'RFC 4519' X-DEPRECATED 'commonName' ) attributeTypes: ( 2.5.4.3 NAME ( 'cn' 'commonName', 'extraPossibleNameHere' ) SUP name X-ORIGIN 'RFC 4519' X-DEPRECATED 'commonName' )
For migration from others LDAP, extending aliases can be useful. At the moment such definition being equal there is a risk to override an extended definition.
since 1.2.11 (schema learning feature)
Risk to loose a alias definition of an attribute
Alias definition should be preserved
Change to be done in schema_at_compare that currently supports single/multi, MR and syntax but not aliases
Metadata Update from @tbordaz: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue priority set to: normal - Issue set to the milestone: 1.4.3
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/3978
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.