multivalue ldap attributes
Pavlos Drandakis
pdrados at noc.edunet.gr
Mon Sep 8 05:14:55 EDT 2008
Hello Scott,
Thanks for your answer. I asked on the PersonDirectory list as you
suggested and here is their response:
<snippet>
This is likely due to the API that CAS is calling to get the attributes.
If you look at
http://developer.ja-sig.org/projects/person-directory/1.1.1/apidocs/org/jasig/services/persondir/IPersonAttributeDao.html
There are two ways to get user attributes:
Map<String, Object> getUserAttributes()
Map<String, List<Object>> getMultivaluedUserAttributes()
CAS would need to be updated to call to the multivalued version of the
API and be able to handle multi-valued attributes.
</snippet>
Is it possible to update cas server core to include this update?
Thanks,
Pavlos
Scott Battaglia wrote:
> Pavlos,
>
> I'm not too familiar with the PersonDirectory. You may wish to ask on
> the PersonDirectory list:
>
> http://www.ja-sig.org/wiki/display/JSG/Person+Directory+Lists
>
> -Scott
>
> -Scott Battaglia
> PGP Public Key Id: 0x383733AA
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
>
> On Thu, Sep 4, 2008 at 5:30 AM, Pavlos Drandakis
> <pdrados at noc.edunet.gr <mailto:pdrados at noc.edunet.gr>> wrote:
>
> Hello all,
>
> I 'm using CAS 3.3 and I 'm trying to populate principal' s attributes
> with ldap repository.
>
> By following http://www.ja-sig.org/wiki/display/CASUM/Attributes
> instructions, I managed to have a working configuration. Everything
> seems to work fine except multivalue attributes. As you can see
> from the
> following snippet from the log file, newRole is a multivalue attribute
> but it is flattened down to a single value.
>
> [DEBUG] Flattened Map='{newRole=[749, 1958, 2762, 2763, 3134, 3146,
> 3158, 3170, 1505]}' into Map='{newRole=749}' -
> org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao
>
> In deployerConfigContext.xml there is
> <property name="ldapAttributesToPortalAttributes">
> <map>
> <entry key="role" value="newRole" />
> </map>
> </property>
>
> Is this the intended behaviour or there is something wrong in my
> configuration?
>
> Thanks in advance,
> Pavlos
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu <mailto:cas at tp.its.yale.edu>
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
More information about the cas
mailing list