directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From directory-...@incubator.apache.org
Subject [jira] Closed: (DIRSNICKERS-83) See if we can connect to the retrofitted LDAPd server using Snickers
Date Thu, 26 Aug 2004 04:51:20 GMT
Message:

   The following issue has been closed.

   Resolver: Alex Karasulu
       Date: Wed, 25 Aug 2004 9:50 PM

Well it looks like its working.  Ethereal captures showed everything going well as I was able
to bind, search and unbind via JNDI.  The OpenLDAP clients however produce a problem because
they query the server's RootDSE and try to perform a SASL bind even when a simple bind is
attempted.  The libraries did not seem to do this before however I cannot pinpoint exactly
why the server is failing at the moment.  It could be because backend resolution of the RootDSE
is failing or the client is in fact attempting a SASL bind which is not yet implemented. 
Regardless I can figure this one out later because I do know for sure via ethereal and the
server logs that the encoder and decoder are working. Correct codec operation was after all
the purpose for this test.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSNICKERS-83

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-83
    Summary: See if we can connect to the retrofitted LDAPd server using Snickers
       Type: Test

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Directory Snickers
 Components: 
             LDAP Provider

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Thu, 29 Jul 2004 7:11 PM
    Updated: Wed, 25 Aug 2004 9:50 PM
    Due:     Sat, 31 Jul 2004 12:00 AM

Description:
Let's get the integration work done and see if LDAPd now works using Snickers.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message