> I am not sure if it is the "right" configuration, but it seems to work...
>
> <bean id="attributeRepository"
>
> class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
> <property name="baseDN" value="ou=people,dc=X,dc=Y" />
> <property name="contextSource" ref="contextSource"/>
> <property name="queryTemplate" value="{0}"/>
>
> <property name="queryAttributeMapping">
> <map>
> <entry key="username" value="uid"/>
> </map>
> </property>
>
> <property name="resultAttributeMapping">
> <map>
> <entry key="ldapAttribute"
> value="applicationAttribute"/>
> </map>
> </property>
> </bean>
>
> Hope it helps
Actually, that helped signficantly. Stepping through a unit test was
leading me to realize that "username" is the default key in the query
part. In any case I got it working and I'll update the Attributes
page with this info. Hopefully a brave soul can figure out how the
JDBC DAO has changed and provide an example of it as well.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
