Re: (ITS#3630) [JLDAP] GetBindID extended operation gives ClassCastException

Tuesday, 27 November 2007

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.

--=__Part5C7A5B2F.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, =
if it still persists.

--=__Part5C7A5B2F.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-15=
">
<META content=3D"MSHTML 6.00.2900.3157" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">
<DIV>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.&nbsp;=
 However one should not get such exceptions, which you've reported even on =
the other LDAP servers (as Active Directory). </DIV>
<DIV>&nbsp;</DIV>
<DIV>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 =
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Login succeeded <BR>Error: LDAPException: Protocol Error (2) Protocol =
ErrorLDAPException: Server Message: 0000203D: LdapErr: DSID-0C090C7D, =
comment: Unknown extended request OID, data 0, vece </DIV>
<DIV>&nbsp;</DIV>
<DIV>which is the expected behavior.</DIV>
<DIV>&nbsp;</DIV>
<DIV>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, if it still persists.</DIV></BODY></HTML>

--=__Part5C7A5B2F.0__=--

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006