On 20/10/10 16:35, Marvin Addison wrote:
I believe this is wrong. The top-most attribute repository bean must
be called attributeRepository, so you'd want
MergingPersonAttributeDaoImpl to have the name "attributeRepository"
and the delegated attribute repository to have another name. We do
something very similar in our environment, and this strategy works
well for us.
I must admit I'm doubtful the bean naming issue I described above is
preventing attributes from being released, but let's fix that and see
where it gets us.
M
I had already changed the naming but that didn't improve things at all.
This is how it looks:
<bean id="attributeRepository"
class="org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl">
<property name="personAttributeDaos">
<list>
<ref bean="ldapAttributeRepository" />
</list>
</property>
<property name="merger">
<bean
class="org.jasig.services.persondir.support.merger.MultivaluedAttributeMerger"/>
</property>
</bean>
<bean id="ldapAttributeRepository"
class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
<property name="contextSource" ref="contextSource" />
<property name="baseDN" value="dc=example,dc=com" />
<property name="requireAllQueryAttributes" value="false" />
<property name="queryAttributeMapping">
<map>
<entry key="username" value="mail" />
</map>
</property>
<property name="resultAttributeMapping">
<map>
<entry key="uid" value="uid" />
<entry key="mail" value="mail" />
<entry key="cn" value="cn"/>
<entry key="telephoneNumber" value="telephoneNumber" />
<entry key="givenname" value="givenname" />
<entry key="sn" value="sn" />
</map>
</property>
</bean>
Giannis
--
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
