As I'm deep in the middle of #50544, I have noticed during this that there are two core attributes that are inconsistent to openldap:
SchemaAttributeInconsistent -> ( 2.5.4.7 NAME ( 'l' 'locality' 'localityname' ) SUP name EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'RFC 4519' ) to ('l', 'localityName') SchemaAttributeInconsistent -> ( 2.5.4.42 NAME 'givenName' SUP name EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'RFC 4519' ) to ('givenName', 'gn')
While the migration tool can handle this, as these are both pretty fundamental it would be better to "pre-resolve" these manually in the project, rather than expecting our users to "fix" these on their instances which may leave them in an unsupportable (or surprising) configuration in 99user.ldif.
For a migration openldap->389-ds, the definition 'l' in 389-ds should not be a problem. syntax/MR are identical only aliases differs but 389-ds aliases of 'l' are a superset of openldap so migration to 389-ds should not create a problem
For givenName, I think it would be acceptable to add 'gn' to 389-ds definition. It requires that https://pagure.io/389-ds-base/issue/50925 to be sure the extended definition will be replicated
Metadata Update from @tbordaz: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
PR https://pagure.io/389-ds-base/pull-request/50946
Metadata Update from @firstyear: - Issue close_status updated to: fixed - 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/3998
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.