You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2016/12/07 13:38:58 UTC

[jira] [Commented] (DIRSERVER-1651) rfc 4533 implementation differences between openldap and apacheDS

    [ https://issues.apache.org/jira/browse/DIRSERVER-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728792#comment-15728792 ] 

Pierre Smits commented on DIRSERVER-1651:
-----------------------------------------

Is this still an issue? Is this project to blame? Or OpenLdap?

> rfc 4533 implementation differences between openldap and apacheDS
> -----------------------------------------------------------------
>
>                 Key: DIRSERVER-1651
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1651
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M2
>            Reporter: Hans-Joachim Kliemeck
>            Assignee: Kiran Ayyagari
>              Labels: 4533, openldap, syncrepl
>             Fix For: 2.0.0-RC1
>
>
> Tthere is an incompatibility between the RFC 4533 implementation of apacheDS and openldap.
> openldap uses the cookie structure "rid=<replicaId>" (initial) or "rid=<replicaId>,csn=<Csn value>" (update) while apacheDS is using NULL for the initial state and the structure "<replicaId>;<Csn value>" for the update state. in the RFC its said:
> {quote}
> The absence of a cookie or an initialized synchronization state in a cookie indicates a request for initial content.....
> {quote}
> first is apacheDS like, second is openldap like
> It should be possible to adapt the structure or the behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)