[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP-2.0 bug: incomplete LDAP_RES_SEARCH_REFERENCE?

At 06:24 PM 11/10/00 +0000, Konstantin Chuguev wrote:
>Hi All,
>In openldap-current/libraries/libldap/result.c I can see:
> * LDAPv3 (RFC2251)
> *      LDAPResult ::= SEQUENCE {
> *              resultCode              ENUMERATED { ... },
> *              matchedDN               LDAPDN,
> *              errorMessage            LDAPString,
> *              referral                Referral OPTIONAL
> *      }
> *      Referral ::= SEQUENCE OF LDAPURL        (one or more)
> *      LDAPURL ::= LDAPString                  (limited to URL chars)
> */
>It appears that matchedDN is missing in LDAP reference result messages.

There is no LDAPResult sequence (which a matchedDN is part of) in a
LDAP SearchResultReference PDU.

>You can check it yourselves:
>./ldapsearch -H ldap://ldap.nameflow.net:389 -s one -b 'dc=org, dc=uk'
>-x 'objectClass=*' ref '*'
>I was stuck digging in those BER structures in C sources, so I have just
>traced LDAP messages in my network :-) The only string informationi in
>these reference result messages is LDAP URL itself.

        SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL

>Or I'd be
>happy if anybody can explain me that this is expected behaviour.

I believe the behavior of search reference results in OpenLDAP
is consistent with the specification.