We upgraded CAS to 4.0.0 and noticed that there are some applications that are
getting the uid attribute via the principal vs. the getRemoteUser() method. We
noticed that CAS is not bringing back this attribute along with the rest. It is
configured in the attributes map referenced in the ldapPersonAttributeDao bean.
The service configurations are also set to have this as an allowed attribute.
Is there a reason why this particular attribute is not being returned?
<bean id="ldapAuthenticationHandler"
class="org.jasig.cas.authentication.LdapAuthenticationHandler"
p:principalIdAttribute="uid"
c:authenticator-ref="authenticator"
p:principalAttributeMap-ref="attributes"/>
<bean id="ldapPersonAttributeDao"
class="org.jasig.cas.persondir.LdapPersonAttributeDao"
p:connectionFactory-ref="searchPooledLdapConnectionFactory"
p:baseDN=“${basedn}"
p:searchControls-ref="searchControls"
p:searchFilter="uid={0}"
p:resultAttributeMapping-ref="attributes”/>
…
<util:map id="attributes">
<entry key="uid" value="uid" />
<entry key="sn" value="sn" />
<entry key="displayName" value="displayName" />
..
</util:map>
- Russ
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
