HI!
The docs at http://www.ja-sig.org/wiki/display/CASUM/Attributes contains
the following example for an LDAP-based attribute repository with a
mapping defined from LDAP attributes to CAS Principal attributes:
--------------------------------- snip ---------------------------------
<bean id="attribRepository"
class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
[..]
<property name="ldapAttributesToPortalAttributes">
<map>
<entry key="cn" value="Name"/>
<entry value="Telephone" key="telephoneNumber" />
<entry value="Fax" key="facsimileTelephoneNumber" />
</map>
</property>
</bean>
--------------------------------- snip ---------------------------------
Watching the LDAP traffic with Wireshark I noticed that the attribute
list in the LDAP search request is empty which results in all attributes
being returned. This causes too much unneeded traffic. Imagine LDAP
entries with binary attributes like jpegPhoto or userCertificate.
Wouldn't it be nice to set the attribute list in the LDAP search request
to the required attributes specified above?
Ciao, Michael.
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
