[mroach]

I just checked the client and using dscl ant thhe /Search within dscl. The only change which i do recognize is the addition of NFSHomeDirectory to the path i’ve specified within the augments under wgm.

The other issue i’m noticing when using wgm to do the augments to the directory, that i still can not add simple attributes. For example, i just tried to put an IMHandle attribute in the augment, but it still would add. I have this added in the augmentconfiguration within the XMLPlist. Still no change saying that this attribute is not mapped.

[mroach]

Without augmenting augmenting the NFShome i had mixed successes. I do not know if the augmentation is actually taking place or if the client is authentication to the ldap server at my university. I do know that the augmentation is taking place via reading the SearchNodeConfig.plist but i also checked the DSLDAPv3PlugInConfig.plist and could not find any trace of augmentation.

This brings up a second question, for the client, do i need to have both the ldap directory configured and also open directory or just the open directory? I am running 10.5 server and clients.

I’ve checked our middleware site that runs the ldap directory and the schema does not have NFSHome or any other references in it to a traditional unix directory with those regards. If you would like to see the schema i can show you off the list.

[mroach]

Chefhomer, I had one issue what trying to the initial mapping of the directory, my university requires pam certs to be installed, before anything would work for me, this could be a thought for you.

But, i’ve a slightly different issue following the configuration.
I’ve followed the sample config also. I’ve ran into an issue when actually writing the augments to the user, within the workgroup manager.

My plist for the augment config was entered like this

[code]


Augment Attribute List

dsRecTypeStandard:Users

dsAttrTypeStandard:MCXSettings
dsAttrTypeStandard:MCXFlags
dsAttrTypeStandard:HomeDirectory
dsAttrTypeStandard:NFSHomeDirectory
dsAttrTypeStandard:PrimaryGroupID
dsAttrTypeStandard:UserShell


Augment Directory Node Name
/LDAPv3/box126.atc.**.edu
Augment Search
Augmented Directory Node Name
/LDAPv3/authn.directory.**.edu

[/code]

When i go to augment the NFSHomeDirectory or any element. I get the following error.

[quote]
Attribute not mapped.

The attribute with the name “NFSHomeDirectory” is not mapped for the record type “Augments”. You should report this error to the administrator of your directory server.
[/quote]

I did check my SearchNodeConfig.plist and it is as follows:

[code]


Augment Attribute List

dsRecTypeStandard:Users

dsAttrTypeStandard:MCXSettings
dsAttrTypeStandard:MCXFlags
dsAttrTypeStandard:HomeDirectory
dsAttrTypeStandard:NFSHomeDirectory
dsAttrTypeStandard:PrimaryGroupID
dsAttrTypeStandard:UserShell


Augment Directory Node Name
/LDAPv3/127.0.0.1
Augment Search
Augmented Directory Node Name
/LDAPv3/authn.directory.**.edu
DHCP LDAP

/Sets/20AEDA80-BE94-4205-8FE7-31DDC1A6C927


Search Node Custom Path Array

/LDAPv3/127.0.0.1
/LDAPv3/authn.directory.**.edu

Search Node PlugIn Version
Search Node PlugIn Version 1.7
Search Policy
3

[/code]

The PD which i am using is authn.directory.**.edu, i am able to browse the directory under workgroup manager. I had to do a custom mapping on the server with the directory utility since my university has a unique schema.

I am wondering since the schema at my university is unique and does not have the typical dsAttrTypeStandard fields, is this causing issues with performing the augmentation?

I did check on the clients and the augmentation has been pushed down, and they can also authenticate against the authn.directory.**.edu.

[Author]

Posts