Full_Name: Russell Howe Version: CVS HEAD OS: Linux/Java 1.[45] URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (217.207.158.98) I get the following when trying to execute a GetBindDN extended operation against Active Directory. I don't know whether AD supports the operation or not, but JLDAP doesn't seem to like whatever AD tells it: Exception in thread "Thread-7" java.lang.ClassCastException: com.novell.ldap.asn1.ASN1Sequence at com.novell.ldap.rfc2251.RfcExtendedResponse.getResultCode(RfcExtendedResponse.java:144) at com.novell.ldap.Message.putReply(Message.java:305) at com.novell.ldap.Connection$ReaderThread.run(Connection.java:1201) at java.lang.Thread.run(Thread.java:595) This was using a freshly built CVS HEAD of jldap, as of about 1200 GMT on 4th April 2005. The code I am using is as follows: conn.connect(hostname, port); conn.bind(ldapVersion, bindDN, ((String)webCredential).getBytes("UTF8")); // ... LDAPExtendedResponse response = conn.extendedOperation(new GetBindDNRequest()); LDAPEntry user = null; if (((response.getResultCode()) == LDAPException.SUCCESS) && (response instanceof GetBindDNResponse)) { String bindDNResponse = ((GetBindDNResponse)response).getIdentity(); log.info("You were logged in as: " + bindDNResponse); user = conn.read(bindDNResponse); } else { log.warn("GetBindDN extended operation failed. Perhaps your LDAP server doesn't support it?"); } I can make the complete source available upon request (it's not restricted in any way..)
Modification of the lines around 144 to be: public final ASN1Enumerated getResultCode() { Object o = get(0); System.out.println("get(0) returns " + o); return (ASN1Enumerated)o; } gives: get(0) returns [UNIVERSAL 16] SEQUENCE: { [UNIVERSAL 10] ENUMERATED: 2, [UNIVERSAL 4] OCTET STRING: , [UNIVERSAL 4] OCTET STRING: } Exception in thread "Thread-7" java.lang.ClassCastException: com.novell.ldap.asn1.ASN1Sequence at com.novell.ldap.rfc2251.RfcExtendedResponse.getResultCode(RfcExtendedResponse.java:146) at com.novell.ldap.Message.putReply(Message.java:305) at com.novell.ldap.Connection$ReaderThread.run(Connection.java:1201) at java.lang.Thread.run(Thread.java:595) -- Russell Howe russell_howe@wreckage.org Today's Nemi: http://www.metro.co.uk/img/pix/nemi_apr4.jpg
moved from Incoming to Contrib
changed notes
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.
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, if it still persists.
Hi, Sorry for the delay. With reference to the below quote, could you please let us know, whether you face the issue still with the latest source? Thanks, Palaniappan. > > 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 > > <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. = > However one should not get such exceptions, which you've reported even on = > the other LDAP servers (as Active Directory). </DIV> > <DIV> </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> </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> </DIV> > <DIV>which is the expected behavior.</DIV> > <DIV> </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, it it still persists.</DIV></BODY></HTML> > > --=__Part6A4C6D19.0__=-- > >
changed state Open to Feedback
resent 3630.reply.1
Please , look at the bug . As it has been for a long time in the feedback state . Please check with the latest source code if the problem is replicated and if it does not please move the bug to closed state . We will be moving it to suspend state after a couple of weeks time . If you find it replicated please feel free to repoen the bug .
Please , look at the bug . As it has been for a long time in the feedback state . Please check with the latest source code if the problem is replicated and if it does not please move the bug to closed state . We will be moving it to suspend state after a couple of weeks time . If you find it replicated please feel free to reopen the bug .
changed state Feedback to Open
JLDAP