Bug 499245 - LDAP Extended operation GetBindDNRequest fails to an exref server
Summary: LDAP Extended operation GetBindDNRequest fails to an exref server
Status: CONFIRMED
Alias: None
Product: NDS SDK
Classification: Novell Products
Component: LDAP Java SDK (show other bugs)
Version: Oct 2007 NDK
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Palaniappan N
QA Contact: Anilkumar S
URL:
Whiteboard:
Keywords: Fix_is_Ready
Depends on:
Blocks:
 
Reported: 2009-04-29 13:10 UTC by Forgotten User AFK1vruhG4
Modified: 2010-06-08 18:01 UTC (History)
2 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Ndstrace file (8.01 KB, text/x-log)
2009-04-29 13:17 UTC, Forgotten User AFK1vruhG4
Details
Sample Code (3.64 KB, text/x-java)
2009-04-29 13:19 UTC, Forgotten User AFK1vruhG4
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User AFK1vruhG4 2009-04-29 13:10:51 UTC
GetBindDNRequest fails with error -601 if the authenticated connection information is requested from an exref server. This operation works fine from an authenticated connection to a replica holder.

ldap.jar tested from 2008-08-01 developer library

Steps to duplicate:

1) Create a 2 server tree, no need to partition, or add aditional users.
2) remove all replicas from server2
3) use attached sample code against both servers.

Result
Server1 Success, the DN authenticated with is returned
Server2: Fail , Bind successful, GetBindDNRequest returns -601

From the attached ndstrace.log
 
Calling DSAReadObjectInfo conn:22 for client .admin.novell.AGS_IDM_TREE.
DSAReadObjectInfo failed, no such entry (-601).
Comment 1 Forgotten User AFK1vruhG4 2009-04-29 13:17:17 UTC
Created attachment 288889 [details]
Ndstrace file
Comment 2 Forgotten User AFK1vruhG4 2009-04-29 13:19:53 UTC
Created attachment 288891 [details]
Sample Code
Comment 3 Rajkumar V 2009-04-29 13:54:52 UTC
This needs to be logged in against SDK product. So , changing the product to NDS SDK.