A confusing attribute resolver configuration

[Rod Widdowson]

Daniel would need to confirm but it looks like you can use the
mappingStrategyRef="bean" capability.

In V3.1.2 the bean would need to be declared like this:

    <bean id="mappings"
class="net.shibboleth.idp.attribute.resolver.dc.ldap.impl.StringAttributeVal
ueMappingStrategy"
        p:noResultAnError="true" p:multipleResultsAnError="true">
        <property name="resultRenamingMap">
            <map>
                <entry key="homephone" value="phonenumber" />
            </map>
        </property>
    </bean>

Which unfortunately means using an impl (and hence subject to change) class
name. 

This is not a stable solution so I really cannot recommend it, but I have
entered IDP-838 to get that fixed (and, of course, documented) in 3.2.0

/Rod