Porting advanced v2 resolver config to v3

[Marvin Addison]

I'm having trouble porting the following snippet of a v2 resolver config to
v3:

  <resolver:DataConnector id="edid-entitlement"
    xsi:type="LDAPDirectory"
    xmlns="urn:mace:shibboleth:2.0:resolver:dc"
    ldapURL="%{idp.attribute.resolver.LDAP.ldapURL}"
    baseDN="ou=entitlements,dc=vt,dc=edu"
    useStartTLS="true"
    authenticationType="EXTERNAL">

    <!-- Entitlement query is based on uid attribute -->
    <resolver:Dependency ref="edid" />

    <FilterTemplate>
      <![CDATA[
        (entitled=uid=$uid.get(0),ou=people,dc=vt,dc=edu)
      ]]>
    </FilterTemplate>
    ...
  </resolver:DataConnector>

The intent is to use the value of the uid attribute resolved from a data
connector dependency, "edid", in the filter expression of the dependent
connector. I believe I have configured the v3 resolver correctly, but it
appears that the "$uid.get(0)" part of the expression is not being
interpreted:

2015-02-10 15:39:57,020 - DEBUG
[net.shibboleth.idp.attribute.resolver.dc.ldap.impl.TemplatedExecutableSearchFilterBuilder:202]
- Template text (entitled=uid=$uid.get(0),ou=people,dc=vt,dc=edu) yields
(entitled=uid=$uid.get(0),ou=people,dc=vt,dc=edu)

I assume this can be made to work in v3 somehow, but I'm at a loss.
Suggestions?

Thanks,
M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150210/d7e6ca54/attachment.html