Hi, have a problem access LDAP and reading 2 OUs in parallel trees.

[Leonard Kroll]

Hi, have a problem accessing LDAP and reading 2 OUs in parallel trees.
I thought the Shib wiki said to use two dependencies from each attribute
to the data connectors.
This causes both OUs to be read from ldap.
 
Example:
<resolver:AttributeDefinition xsi:type="ad:Simple" id="samaccountname"
sourceAttributeID="sAMAccountName"
xmlns="urn:mace:shibboleth:2.0:resolver:ad">
<resolver:Dependency ref="myLDAP" />
<resolver:Dependency ref="my2LDAP" />
<resolver:AttributeEncoder xsi:type="enc:SAML1String" 
name="urn:mace:dir:attribute-def:sAMAccountName" />
<resolver:AttributeEncoder xsi:type="enc:SAML2String"
name="urn:oid:1.2.840.113556.1.4.221" 
 
friendlyName="sAMAccountName" />
</resolver:AttributeDefinition>
 
It works if the user is found in the 2nd data connectors OU.
If the user is found in the 1st data connector's OU, I get an error from
the 2nd data connector, and no attributes are returned to the SP.
 
I am required by security to use https, port 636.
Is there a better way to do this?
 
Leonard Kroll
UNIX / GIS Administrator
Univ. Massachusetts Boston
Leonard(dot)Kroll(at)umb.edu <mailto:at at umb.edu> 
Phone: 617-287-5048
fax:      617-287-5224
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20111212/d14f4484/attachment.html