Shibboleth Developers

[Chad La Joie <>]

The dependencies that you list are things upon which the plugin depends
NOT things that depend on the plugin.  So, in your example the attribute
definition depends on the LDAP data connector, not the other way around.
 So, nothing went wrong.  You seem to not understand what the word
"dependency" means, or at least the difference between a dependency and
a dependent.

Markus Ludwig Grandpre wrote:
> I wonder how the Shibboleth2 LdapDataConnector gains access to any
> AttributeDefinition object that declares a reference/dependency to this
> connector e.g.
> 
> <resolver:AttributeDefinition
>  id="eduPersonEntitlement"
>  ...
>  <resolver:Dependency ref="myLDAP" />
> 
> whereby the DataConnector of the LdapDataConnector does not
> declare any dependency to AttributeDefinitions at all:
> 
> <resolver:DataConnector
>   id="myLDAP"
>   xsi:type="LDAPDirectory"
>   xmlns="urn:mace:shibboleth:2.0:resolver:dc"
>   ...
>  </resolver:DataConnector>
> 
> I've followed the LdapDataConnector implementation and used parts of it
> for my own DataConnector implementation, but getting null values all the
> time.
> 
> What went wrong?


-- 
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Net Services
Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
,
 http://www.switch.ch