> This shows an attribute map. The CAS client is still failing with the “out > of range” message. Are there updated CAS java client libraries or would I be > better to go with PHP clients for the moment?
Pretty sure it's not a client issue. I have working configurations for the common configurations we will support, but have not updated documentation yet, but will do so early next week. In any case you will need to define an attributeRepository bean of type IPersonAttributeDao. That happens naturally in CAS 3.5 when configuring a CredentialsToPrincipalResolver, but with that component optional in 4.0 it's not entirely clear how to handle it. I would recommend StubPersonAttributeDao [1] that is configured with the same attribute names as that defined for LdapAuthenticationHandler but with dummy values. Its only purpose is to provide a list of attribute names for consumption by the service management facility in filtering attributes on a per-service basis. I will attempt to document this case clearly when I put up the final LDAP handler configurations next week. M [1] https://github.com/Jasig/person-directory/blob/master/person-directory-impl/src/main/java/org/jasig/services/persondir/support/StubPersonAttributeDao.java -- 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-dev
