Apache Directory Project - [jira] Commented: (DIRLDAP-51) Incorrect matched DN in the bind response (and others d

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > October 2005 > [jira] Commented: (DIRLDAP-51) Incorrect matched DN in the bind response (and others d





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (DIRLDAP-51) Incorrect matched DN in the bind response (and others d
Emmanuel Lecharny (JIRA)

2005-10-29, 2:45 am

[ http://issues.apache.org/jira/brows...comments#actio=
n_12356254 ]=20

Emmanuel Lecharny commented on DIRLDAP-51:
------------------------------------------

This bug is related to RFC 2251. It's not any more a bug for http://www.iet=
f.org/internet-drafts/draft-ietf-ldapbis-protocol-32.txt, 4.1.9 :
"For certain result codes (typically, but not restricted to=20
noSuchObject, aliasProblem, invalidDNSyntax and=20
aliasDereferencingProblem), the matchedDN field is set (subject to=20
access controls) to the name of the last entry (object or alias) used=20
in finding the target (or base) object. This will be a truncated form=20
of the provided name or, if an alias was dereferenced while=20
attempting to locate the entry, of the resulting name. Otherwise the=20
matchedDN field is empty. "

A flag could be added in configuration to address the possibility to handle=
ldap-v3 or ldap-bis specific cases.

> Incorrect matched DN in the bind response (and others depending on the re=

sult code)
> -------------------------------------------------------------------------=

----------
>
> Key: DIRLDAP-51
> URL: http://issues.apache.org/jira/browse/DIRLDAP-51
> Project: Directory LDAP
> Type: Bug
> Components: Common
> Versions: 0.9.2
> Reporter: J=C3=A9r=C3=B4me Baumgarten
> Priority: Trivial


>
> According to RFC 2251 [1], section "4.1.10. Result Message", the matched =

DN for a bind response should be a zero length string.
> I believe that other handlers should also be reviewed according to the fo=

llowing :
> For result codes of noSuchObject, aliasProblem, invalidDNSyntax and
> aliasDereferencingProblem, the matchedDN field is set to the name of
> the lowest entry (object or alias) in the directory that was matched.
> If no aliases were dereferenced while attempting to locate the entry,
> this will be a truncated form of the name provided, or if aliases
> were dereferenced, of the resulting name, as defined in section 12.5
> of X.511. The matchedDN field is to be set to a zero length
> string with all other result codes.
> J=C3=A9r=C3=B4me
> [1] : http://www.ietf.org/rfc/rfc2251.txt


--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com