Bug 124389 (DEFECT000315111)

Summary:	Need to be smarter about following referrals
Product:	[Novell Products] NDS SDK	Reporter:	Alan Clark <aclark>
Component:	LDAP C SDK	Assignee:	Alan Clark <aclark>
Status:	VERIFIED WONTFIX	QA Contact:	Sundar Swamy <ssundar>
Severity:	Minor
Priority:	P5 - None	CC:	aclark
Version:	OCT 2006 NDK	Keywords:	English
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:	SCRUB
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rajkumar V 2005-10-10 22:54:50 UTC



------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000315111 at remedy/
remedy/show_bug.cgi?id=DEFECT000315111
Originally filed under the NDS SDK product and LDAP C SDK component.

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> Can we be smarter about following encrypted vs
      non-encrypted referrals in CLDAP? </remedy_details>
---------
<remedy_notes> dsteck (  2/24/2003 4:25:34 PM  Fixing - Approved for
      Investigation ) I noticed that Kurt Zeilenga has an item in the OpenLDAP
      To-Do list called:
    Implement per referral/continuation callback

It sounds like they�re thinking about a system where a rebind function gets
all the referrals at once and can decide among them, rather than getting one
at a time and having to try it and give a pass/fail.  This seems like the
right approach.  You may want to discuss the details of this with Kurt, so
we don�t duplicate effort and so that we end up with a solution compatible
with OpenLDAP.

 </remedy_notes>

Comment 1 Hiredesai Santosh 2006-07-21 11:48:57 UTC

The SDK team has worked out a realistic set of defects, one that will actually be fixed in the upcoming NDK's.There are currently 60 CLDAP sdk Bugs and enhancements.  Our plan is to close the bugs reported before 2004 and have not been reported in the recent past. This Bug is a prime candidate to be closed.
If you think that it should remain open, add an additional short comment explaining why.The CCB will go through all of these updated defects and determine if and when they can be fixed.

This must be done by 15th August 2006 .After that this defect will be closed.

Comment 2 Hiredesai Santosh 2006-08-18 04:09:59 UTC

Will not be fixing the bug as we have not heard back from the reporter.

Comment 3 Hiredesai Santosh 2006-08-18 04:10:24 UTC

closing the bug..