#58 Replication agreements contain attributes which have invalid syntax
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by mkosek.

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

Reported by Andrey Ivanov (andrey.ivanov@polytechnique.fr)

Description of problem:
However, i still have the syntax validation problem in cn=config for
replication agreements (have not tested with 1.2.8rcx but i think it has not
changed):

nsds5replicaChangesSentSinceStartup: value #0 invalid per syntax
nsds5replicaLastInitStart: value #0 invalid per syntax
nsds5replicaLastInitEnd: value #0 invalid per syntax

I think it's not the dn parsing problem, it is the schema definitions of
syntaxes for these attributes and the values that do not correspond to the
syntax :

(has integer syntax)nsds5replicaChangesSentSinceStartup: 1:11157/0 3:176/0
(has generalized time syntax)nsds5replicaLastInitStart: 0
(has generalized time syntax)nsds5replicaLastInitEnd: 0


attributeTypes: ( 2.16.840.1.113730.3.1.687 NAME
'nsds5replicaChangesSentSinceStartup' DESC 'Netscape defined attribute type'
EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

attributeTypes: ( 2.16.840.1.113730.3.1.807 NAME 'nsds5replicaLastInitStart'
DESC 'Netscape defined attribute type' EQUALITY generalizedTimeMatch ORDERING
generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

attributeTypes: ( 2.16.840.1.113730.3.1.808 NAME 'nsds5replicaLastInitEnd' DESC
'Netscape defined attribute type' EQUALITY generalizedTimeMatch ORDERING
generalizedTimeOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 SINGLE-VALUE
NO-USER-MODIFICATION X-ORIGIN 'Netscape Directory Server' )

Note: Separated from Bug 555577 - Syntax validation fails for "ou=NetscapeRoot"
tree

batch move to milestone future

set default ticket origin to Community

Added initial screened field value.

A good timing to fix this?

Per triage, set to FUTURE.

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

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 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/58

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: fixed)

3 years ago

Login to comment on this ticket.

Metadata