>>ITEM: N00076
>>DATE: 07/09/96
>>TYPE: Information
>>TITLE: N_D_SCAN and N_D_WHOAMI return fully qualified names
>>PRODUCT(S):
NetLib 6.5x for Clipper
>>PLATFORM(S):
NetWare 4.1 NDS with VLM services
>>SUMMARY:
Names returned from N_D_WHOAMI, N_D_SCAN, N_D_MEMBERS, etc.,
are fully qualified names rather than relative names.
>>MORE INFORMATION:
A fully qualified name (also called a Distinguished Name or DN) is based from the root context.
For example, the user THISUSER in Organizational Unit THISDEPT in Organization THISORG would have a fully qualified name of THISUSER.THISDEPT.THISORG.
If the current context were THISDEPT.THISORG, then the
relative name (also called a relative distinguished name or RDN)
would simply be THISUSER.
>>RESOLUTION/FIX:
Use the undocumented NetLib function N_D_NAMING. This function
sets/gets the NDS Context flags. The syntax is:
{nCurrentSetting} := N_D_NAMING({nNewSetting})
{nNewSetting} has many potential values, but the value that
affects DN or RDN names is 16. Since the setting is a
bitmap, not a value, you should use A_OR() to set the
appropriate bit value.
>>EXAMPLE(S):
#define DCV_CANONICALIZE_NAMES 16
* set relatve names (RDN)
N_D_NAMING(A_OR(N_D_NAMING(),DCV_CANONICALIZE_NAMES))
? N_D_WHOAMI()
THISUSER
* set fully qualified names (DN)
N_D_NAMING(A_AND(A_D_NAMING(),-1-DCV_CANONICALIZE_NAMES))
? N_D_WHOAMI()
THISUSER.THISDEPT.THISORG
>>SEE ALSO: N00075
>>COPYRIGHT 1997 Communication Horizons
All rights reserved worldwide.
No distribution without specific consent of publisher.
Knowledgebase
Top Home