#47811 duplicate matching rule names in cn=schema
Closed: wontfix None Opened 7 years ago by rmeggins.

ldapsearch -xLLL -s base -b "cn=schema" matchingRules|grep -i caseIgnoreOrderingMatch-bn

matchingRules: ( 2.16.840.1.113730.3.3.2.76.1 NAME 'caseIgnoreOrderingMatch-bn
matchingRules: ( 2.16.840.1.113730.3.3.2.77.1 NAME 'caseIgnoreOrderingMatch-bn
matchingRules: ( 2.16.840.1.113730.3.3.2.78.1 NAME 'caseIgnoreOrderingMatch-bn

There are many others. The problem is that we are automatically creating the name of the matching rule from the collation file, using only the locale and not the region:

ldap/schema/slapd-collations.conf:collation bn BD "" 1 3 2.16.840.1.113730.3.3.2.77.1 bn-BD

I think we either need to use the full locale-region-subregion in the name of the matching rule, or somehow otherwise make sure the name is unique.

Note: This causes problems with web2ldap schema viewing, and will probably cause problems with other LDAPv3 compliant clients.


It is not a duplicate...
{{{
matchingRules: ( 2.16.840.1.113730.3.3.2.76.1 NAME 'caseIgnoreOrderingMatch-bn' DESC 'bn' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
matchingRules: ( 2.16.840.1.113730.3.3.2.77.1 NAME 'caseIgnoreOrderingMatch-bn-BD' DESC 'bn-BD' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
matchingRules: ( 2.16.840.1.113730.3.3.2.78.1 NAME 'caseIgnoreOrderingMatch-bn-IN' DESC 'bn-IN' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
}}}

Also, I think there's no other duplicates, too...
{{{
$ ldapsearch -LLLx -s base -b "cn=schema" -o ldif-wrap=no matchingRules | egrep -i matchingrules | wc -l
525
$ ldapsearch -LLLx -s base -b "cn=schema" -o ldif-wrap=no matchingRules | egrep -i matchingrules | sort | uniq | wc -l
525
}}}
Closing this ticket as not a bug...

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.3 backlog

5 years ago

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

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 (was: Invalid)

2 years ago

Login to comment on this ticket.

Metadata