DS HELP JASON TOWNSEND
DS HELP JASON TOWNSEND
- Subject: DS HELP JASON TOWNSEND
- From: "Mr. Wong" <email@hidden>
- Date: Tue, 09 Nov 2004 15:37:57 -0800
Jason,
Yes that helps very much....I do, however, have one more question. You are
saying that my "directory access" mapping settings enable me to view
specified nodes from the LDAP server. With this info in mind I tried
"browsing" the LDAP server with dscl. To my dismay I was NOT able to browse
the node of interest (cn = Persons). I tweaked the directory access
mappings to my hearts conent and still haven't been able to browse the
desired node....
Any suggestions?
Thanks,
--Matthew.
------------------------------
Message: 2
Date: Mon, 1 Nov 2004 18:58:07 -0800
From: Jason Townsend <email@hidden>
Subject: Re: DS Help
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: "Mr. Wong" <email@hidden>
I am looking for some help with DS....I've been in contact with Finlay
Dobie and he suggested I look here for Jason Townsend.
Here is my problem... I've managed to do a dsDoAttributeValueSearch and
pull some custom records / attributes of interest from the local NetInfo
directory (by modifying the DSTestTool that came with the DS SDK). I've
also managed to get "SOME" results from a a full blown LDAP server, but I'm
having trouble specifying custom NODES with custom attributes.... .... I
need to search a node with a cn = Persons... is there any easy way of doing
this? Also how can I search for Custom attributes as opposed to standard
or native.
In general we encourage developers to use standard types. Native types
should only be used as a last resort when a standard type is not
available.
In the case of LDAP, native record types are currently not supported.
The mappings set up in Directory Access determine the search base,
scope, and optionally a list of object classes to filter on, so it
wasn't quite as straightforward to pass all that information through
the native record type name as it is in NetInfo.
Native attributes are supported on LDAP, these are simply the native
prefix followed by the name of the attribute in LDAP (for example, what
you would see in the output of ldapsearch).
In the case of cn=Persons, I suspect that either you want to use the
People record type which is for storing inetOrgPerson/Address Book
types of information, or you want the Users record type which can
include login information as well as the inetOrgPerson/Address Book
information. I would recommend you map one of these record type.
I'm not sure what you mean by "custom" attributes... the standard vs.
native distinction is fairly straightforward. The standard attribute
types are defined in the Directory Services headers and documentation,
and represent a namespace which can be used across multiple directory
systems. The native attributes are specific to a particular directory
system (or even a particular node), and represent that specific
namespace as it is actually stored. The various plug-ins have to map
between the standard and native types. For LDAP, any attribute which
has the native prefix is interpreted to mean exactly the attribute name
that follows the prefix.
P.S. Where is the easiest source for the mapping between Directory
Services and LDAP.... I've been usiing the "Directory Access" utility..
Directory Access is the best tool to set up/inspect LDAP mappings at
the moment. Is that what you were asking?
Hope that helps,
-Jason
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden