#215 Missing support for required syntaxes
Closed: wontfix None Opened 12 years ago by rmeggins.

https://bugzilla.redhat.com/show_bug.cgi?id=477686

Description of problem:


When loading the LDIF file with the proposed schema for v2 it complains about
the following syntaxes:

1.3.6.1.4.1.1466.115.121.1.8 - Certificate syntax
1.3.6.1.4.1.1466.115.121.1.9 - Certificate List syntax
1.3.6.1.4.1.1466.115.121.1.10 - Certificate Pair syntax

1.3.6.1.4.1.1466.115.121.1.36 - Numeric String syntax

First 3 are used by our certificate integration schema:
https://idmwiki.sjc.redhat.com/export/idmwiki/DS_Design_Summary#Certificate_Rel
ated_Attributes_and_Objects
and based on the RFC 4523.

The last one is required by DNS integration.



How reproducible:
Always

Load the ldif with following lines:

  attributeTypes: ( 2.5.4.37 NAME 'cACertificate'
             DESC 'X.509 CA certificate'
             EQUALITY certificateExactMatch
             SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 )

  attributeTypes: ( 2.5.4.40 NAME 'crossCertificatePair'
             DESC 'X.509 cross certificate pair'
             EQUALITY certificatePairExactMatch
             SYNTAX 1.3.6.1.4.1.1466.115.121.1.10 )

  attributeTypes: ( 2.5.4.39 NAME 'certificateRevocationList'
             DESC 'X.509 certificate revocation list'
             EQUALITY certificateListExactMatch
             SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 )

  attributeTypes: ( 2.16.840.1.113730.3.8.3.40
        NAME 'idnsSOAminimum'
        DESC 'SOA minimum value'
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.36
        SINGLE-VALUE
        X-ORIGIN 'IPA v2' )

ALSO, if one changes the SYNTAX to a known one the system does not complain
about the EQUALITY that it probably does not know anything about.

batch update moving tickets to future

I believe that this work is already done, but we should cross-check the code before closing this ticket.

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: FUTURE

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

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)

3 years ago

Login to comment on this ticket.

Metadata