From rarpit@novell.com Wed Nov 28 06:52:22 2007
From: rarpit@novell.com
To: openldap-bugs@openldap.org
Subject:
Re: (ITS#3630) [JLDAP] GetBindID extended operation gives ClassCastException
Date: Wed, 28 Nov 2007 06:52:22 +0000
Message-ID: <200711280652.lAS6qMcj052661@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2001410650894806782=="
--===============2001410650894806782==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__Part6A4C6D19.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Generally, the extensions (extended operations) are not common to all the =
LDAP servers. Most of the extensions available here as part of jldap(includ=
ing the GetBindDN) are exensions supported by eDirectory. However one =
should not get such exceptions, which you've reported even on the other =
LDAP servers (as Active Directory).=20
=20
However, I tried the same code as stated on AD server and I didn't get the =
exception you got. Instead I am getting the following exceptions=20
=20
Login succeeded=20
Error: LDAPException: Protocol Error (2) Protocol ErrorLDAPException: =
Server Message: 0000203D: LdapErr: DSID-0C090C7D, comment: Unknown =
extended request OID, data 0, vece=20
=20
which is the expected behavior.
=20
Please check the issues once again with the latest JLDAP code and please =
do let me know if I need to do something more for replicating the problem, =
it it still persists.
--=__Part6A4C6D19.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Generally, the extensions (extended operations) are not common to all =
the LDAP servers. Most of the extensions available here as part of =
jldap(including the GetBindDN) are exensions supported by eDirectory. =
However one should not get such exceptions, which you've reported even on =
the other LDAP servers (as Active Directory).
However, I tried the same code as stated on AD server and I didn't =
get the exception you got. Instead I am getting the following exceptions =
Login succeeded
Error: LDAPException: Protocol Error (2) Protocol =
ErrorLDAPException: Server Message: 0000203D: LdapErr: DSID-0C090C7D, =
comment: Unknown extended request OID, data 0, vece
which is the expected behavior.
Please check the issues once again with the latest JLDAP code and =
please do let me know if I need to do something more for replicating the =
problem, it it still persists.
--=__Part6A4C6D19.0__=--
--===============2001410650894806782==--