directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-853) Ldap ref values incorrectly handled for referrals
Date Sat, 25 Aug 2007 14:29:30 GMT


Emmanuel Lecharny commented on DIRSERVER-853:

The RFC text is not that clear : how do we determine that the URI address a LDAP server ?
I guess that if the scheme is 'ldap', then this is the case. Let's assume that.

> Ldap ref values incorrectly handled for referrals
> -------------------------------------------------
>                 Key: DIRSERVER-853
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 1.5.1
> In case we have a referral, and if the LdapURLs stored in the ref values refers to Ldap
serve r(if they start by ldap://), RFC 3296 states that :
> "If the URI contained in a ref attribute value refers to a LDAP
>    [RFC2251] server, it MUST be in the form of a LDAP URL [RFC2255].
>    The LDAP URL SHOULD NOT contain an explicit scope specifier, filter,
>    attribute description list, or any extensions.  The LDAP URL SHOULD
>    contain a non-empty DN"
> The current ReferralService code does not really implement those controls. We can have
empty DNs, scope, filter ... 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message