One of the features that is attractive about CAS is it’s ability to pass LDAP attributes to a specified application via SAML. This functionality is starting to become more heavily used by our web developers, creating demand for more and more attributes to mapped. An issue arose from this; CAS must be rebuilt every time a new attribute is to be mapped. The solution was to externalize the resultAttributeMapping property to a configuration file. This can be achieved through the use of the util schema.
Add the schema to deployerConfigContext.xml:
Append the following to schemaLocation:
The resultAttributeMapping property (in deployerConfigContext) will look like this:
<property name="resultAttributeMapping"> <util:properties id="attr" location="file:/etc/cas/ldap.attributes" /> </property>
Your attributes file cannot contain other property configurations, due to how the file is referenced. It is a collection that follows the form: key=value, with each entry placed on its own line. Here is an example ldap.attributes property file:
cn=cn uid=ssoid givenname=givenName mail=email