Data Connector Depending on Attributes

[Nate Klingenstein]

All,

I’ve got a use case where I need to execute a query against an LDAP directory data connector using the results acquired from a prior query to another system.  I’m screwing up the wiring, apparently.

As far as I’m aware, the employee number is being populated as UID successfully by the first query, but it’s the rest of the mechanics that aren’t working.  Here’s what I’m trying:

   <resolver:AttributeDefinition xsi:type="ad:Simple" id=“firstdotlast" sourceAttributeID=“firstdotlast">
       <resolver:Dependency ref=“OpenDJ" />
       <resolver:AttributeEncoder xsi:type="enc:SAML2String" name=“https://example.org/attributes/firstdotlast" friendlyName=“First.Last" encodeType="false" />
   </resolver:AttributeDefinition>

   <resolver:DataConnector id=“OpenDJ" xsi:type="dc:LDAPDirectory"
       ldapURL="ldaps://ldap.example.org:636"
       baseDN=“ou=people,dc=example,dc=org"
       principal=“authoritativeDN"
       principalCredential="authoritativeDNpasswd"
       useStartTLS="false”>
   
   <resolver:Dependency id=“otherLDAP” />
   
       <dc:FilterTemplate>
           <![CDATA[
              employeeNumber=${uid}
           ]]>
       </dc:FilterTemplate>
   </resolver:DataConnector>

Does anyone see an obvious mistake?

As an aside, I presume horrible things happen if both data sources use the same field for different things and I don’t filter the results.

Thanks,
Nate.