All, I have been struggling with trying to get attributes to properly return for over a week now and I believe I have found an issue where the 4.0.0 documentation refers you back to the "3.5.2" way of doing things. First some background:
We are doing LDAP authentication, and using our LDAP as a service repository. Both those pieces are working correctly as far as we can tell with the SSO server and the hand-entered registered services (we have yet to get the service management webapp working). We are trying to replace the attribute "stub" in deployerConfigContext.xml with an LDAP attribute repository. We have been trying to follow the documentation for the "principal resolver" pieces of the attribute return detailed in http://jasig.github.io/cas/4.0.0/installation/Configuring-Authentication-Components.html. Under the "PrincipalResolver Components" following the persondir "LDAP" link of https://wiki.jasig.org/x/iBjP tells you to create an LdapPersonAttributeDao like so: |<||bean| |id||=||"ldapPersonAttributeDao"| |class||=||"org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao"||>| | ||<||property| |name||=||"contextSource"| |ref||=||"contextSource"| |/>| | ||<||property| |name||=||"baseDN"| |value||=||"o=example.com,o=isp"| |/>| | ||<||property| |name||=||"queryAttributeMapping"||>| | ||<||map||>| | ||<||entry| |key||=||"username"| |value||=||"uid"| |/>| | ||</||map||>| | ||</||property||>| | ||<||property| |name||=||"resultAttributeMapping"||>| | ||<||map||>| | ||<||entry| |key||=||"uid"| |value||=||"username"| |/>| | ||<||entry| |key||=||"givenname"| |value||=||"first_name"| |/>| | ||<||entry| |key||=||"sn"| |value||=||"last_name"| |/>| | ||<||entry| |key||=||"mail"| |value||=||"email"| |/>| | ||</||map||>| | ||</||property||>| |</||bean||>| If you have correctly set up your LDAP authentication using the method described in the CAS 4.0.0 documentation for LDAP authentication THIS WILL NOT WORK since there is no contextSource defined in the LdapAuthenticationHandler using the CAS 4.0.0 method. You actually need to use a differently classed LdapPersonAttributeDao (instead of |org.jasig.*services.persondir.support.ldap*.LdapPersonAttributeDao |you must use org.jasig.*cas.persondir*.LdapPersonAttributeDao which uses different properties for setting up the LDAP context). This is what we ended up with for our deployer ConfigContext.xml file (this is the entire file): <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to Jasig under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. Jasig licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at the following location: http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- | deployerConfigContext.xml centralizes into one file some of the declarative configuration that | all CAS deployers will need to modify. | | This file declares some of the Spring-managed JavaBeans that make up a CAS deployment. | The beans declared in this file are instantiated at context initialization time by the Spring | ContextLoaderListener declared in web.xml. It finds this file because this | file is among those declared in the context parameter "contextConfigLocation". | | By far the most common change you will need to make in this file is to change the last bean | declaration to replace the default authentication handler with | one implementing your approach for authenticating usernames and passwords. +--> <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:p="http://www.springframework.org/schema/p"; xmlns:c="http://www.springframework.org/schema/c"; xmlns:tx="http://www.springframework.org/schema/tx"; xmlns:util="http://www.springframework.org/schema/util"; xmlns:sec="http://www.springframework.org/schema/security"; xmlns:context="http://www.springframework.org/schema/context"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.2.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.2.xsd http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.2.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util.xsd";> <context:component-scan base-package="org.jasig.cas" /> <context:component-scan base-package="org.jasig.cas.authentication" /> <!-- | The authentication manager defines security policy for authentication by specifying at a minimum | the authentication handlers that will be used to authenticate credential. While the AuthenticationManager | interface supports plugging in another implementation, the default PolicyBasedAuthenticationManager should | be sufficient in most cases. +--> <bean id="authenticationManager" class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager"> <constructor-arg> <map> <!-- | IMPORTANT | Every handler requires a unique name. | If more than one instance of the same handler class is configured, you must explicitly | set its name to something other than its default name (typically the simple class name). --> <entry key-ref="proxyAuthenticationHandler" value-ref="proxyPrincipalResolver" /> <entry key-ref="ldapAuthenticationHandler" value-ref="primaryPrincipalResolver" /> </map> </constructor-arg> <!-- Uncomment the metadata populator to allow clearpass to capture and cache the password This switch effectively will turn on clearpass. <property name="authenticationMetaDataPopulators"> <util:list> <bean class="org.jasig.cas.extension.clearpass.CacheCredentialsMetaDataPopulator" c:credentialCache-ref="encryptedMap" /> </util:list> </property> --> <!-- | Defines the security policy around authentication. Some alternative policies that ship with CAS: | | * NotPreventedAuthenticationPolicy - all credential must either pass or fail authentication | * AllAuthenticationPolicy - all presented credential must be authenticated successfully | * RequiredHandlerAuthenticationPolicy - specifies a handler that must authenticate its credential to pass --> <property name="authenticationPolicy"> <bean class="org.jasig.cas.authentication.AnyAuthenticationPolicy" /> </property> </bean> <!-- Required for proxy ticket mechanism. --> <bean id="proxyAuthenticationHandler" class="org.jasig.cas.authentication.handler.support.HttpBasedServiceCredentialsAuthenticationHandler" p:httpClient-ref="httpClient" /> <!-- Start the additions for the LDAP authentication here. --> <bean id="ldapAuthenticationHandler" class="org.jasig.cas.authentication.LdapAuthenticationHandler" p:principalIdAttribute="uid" c:authenticator-ref="authenticator"> <property name="principalAttributeMap"> <map> <!-- | This map provides a simple attribute resolution mechanism. | Keys are LDAP attribute names, values are CAS attribute names. | Use this facility instead of a PrincipalResolver if LDAP is | the only attribute source. --> <entry key="uid" value="uid" /> <entry key="mail" value="mail" /> <entry key="cn" value="displayName" /> <entry key="eduPersonPrincipalName" value="eduPersonPrincipalName" /> </map> </property> </bean> <bean id="authenticator" class="org.ldaptive.auth.Authenticator" c:resolver-ref="dnResolver" c:handler-ref="authHandler" /> <bean id="dnResolver" class="org.ldaptive.auth.PooledSearchDnResolver" p:baseDn="${ldap.authn.baseDn}" p:allowMultipleDns="false" p:subtreeSearch="true" p:connectionFactory-ref="searchPooledLdapConnectionFactory" p:userFilter="${ldap.authn.searchFilter}" /> <bean id="searchPooledLdapConnectionFactory" class="org.ldaptive.pool.PooledConnectionFactory" p:connectionPool-ref="searchConnectionPool" /> <bean id="searchConnectionPool" parent="abstractConnectionPool" p:connectionFactory-ref="searchConnectionFactory" /> <bean id="searchConnectionFactory" class="org.ldaptive.DefaultConnectionFactory" p:connectionConfig-ref="searchConnectionConfig" /> <bean id="searchConnectionConfig" parent="abstractConnectionConfig" p:connectionInitializer-ref="bindConnectionInitializer" /> <bean id="bindConnectionInitializer" class="org.ldaptive.BindConnectionInitializer" p:bindDn="${ldap.authn.managerDn}"> <property name="bindCredential"> <bean class="org.ldaptive.Credential" c:password="${ldap.authn.managerPassword}" /> </property> </bean> <bean id="abstractConnectionPool" abstract="true" class="org.ldaptive.pool.BlockingConnectionPool" init-method="initialize" p:poolConfig-ref="ldapPoolConfig" p:blockWaitTime="${ldap.pool.blockWaitTime}" p:validator-ref="searchValidator" p:pruneStrategy-ref="pruneStrategy" /> <bean id="abstractConnectionConfig" abstract="true" class="org.ldaptive.ConnectionConfig" p:ldapUrl="${ldap.url}" p:connectTimeout="${ldap.connectTimeout}" p:useStartTLS="${ldap.useStartTLS}" p:sslConfig-ref="sslConfig" /> <bean id="ldapPoolConfig" class="org.ldaptive.pool.PoolConfig" p:minPoolSize="${ldap.pool.minSize}" p:maxPoolSize="${ldap.pool.maxSize}" p:validateOnCheckOut="${ldap.pool.validateOnCheckout}" p:validatePeriodically="${ldap.pool.validatePeriodically}" p:validatePeriod="${ldap.pool.validatePeriod}" /> <bean id="sslConfig" class="org.ldaptive.ssl.SslConfig"> <property name="credentialConfig"> <bean class="org.ldaptive.ssl.X509CredentialConfig" p:trustCertificates="${ldap.trustedCert}" /> </property> </bean> <bean id="pruneStrategy" class="org.ldaptive.pool.IdlePruneStrategy" p:prunePeriod="${ldap.pool.prunePeriod}" p:idleTime="${ldap.pool.idleTime}" /> <bean id="searchValidator" class="org.ldaptive.pool.SearchValidator" /> <bean id="authHandler" class="org.ldaptive.auth.PooledBindAuthenticationHandler" p:connectionFactory-ref="bindPooledLdapConnectionFactory" /> <bean id="bindPooledLdapConnectionFactory" class="org.ldaptive.pool.PooledConnectionFactory" p:connectionPool-ref="bindConnectionPool" /> <bean id="bindConnectionPool" parent="abstractConnectionPool" p:connectionFactory-ref="bindConnectionFactory" /> <bean id="bindConnectionFactory" class="org.ldaptive.DefaultConnectionFactory" p:connectionConfig-ref="bindConnectionConfig" /> <bean id="bindConnectionConfig" parent="abstractConnectionConfig" /> <!-- End of LDAP authentication insertions --> <!-- Required for proxy ticket mechanism --> <bean id="proxyPrincipalResolver" class="org.jasig.cas.authentication.principal.BasicPrincipalResolver" /> <!-- | Resolves a principal from a credential using an attribute repository that is configured to resolve | against a deployer-specific store (e.g. LDAP). --> <bean id="primaryPrincipalResolver" class="org.jasig.cas.authentication.principal.PersonDirectoryPrincipalResolver" > <property name="attributeRepository" ref="attributeRepository" /> </bean> <!-- Bean that defines the attributes that a service may return. This example uses the Stub/Mock version. A real implementation may go against a database or LDAP server. The id should remain "attributeRepository" though. +--> <!-- <bean id="attributeRepository" class="org.jasig.services.persondir.support.StubPersonAttributeDao" p:backingMap-ref="attrRepoBackingMap" /> <util:map id="attrRepoBackingMap"> <entry key="uid" value="uid" /> </util:map> --> <bean id="attributeRepository" class="org.jasig.cas.persondir.LdapPersonAttributeDao" p:baseDN="${ldap.authn.baseDn}" p:searchFilter="${ldap.authn.searchFilter}" p:searchControls-ref="searchControls" p:connectionFactory-ref="searchPooledLdapConnectionFactory" p:queryAttributeMapping-ref="queryAttributeMap" p:resultAttributeMapping-ref="resultAttributeMap" /> <util:map id="queryAttributeMap"> <entry key="user" value="uid" /> </util:map> <util:map id="resultAttributeMap"> <entry key="uid" value="user" /> <entry key="mail" value="email" /> <entry key="cn" value="displayName" /> <entry key="eduPersonPrincipalName" value="eduPersonPrincipalName" /> </util:map> <bean id="searchControls" class="javax.naming.directory.SearchControls" p:searchScope="2" /> <!-- Service registry over LDAP additions. This is where all the stuff for the service registry needs to be defined. The first set of stuff should be used to set up the LDAP connection Pool. --> <bean id="serviceRegistryDao" class="org.jasig.cas.adaptors.ldap.services.LdapServiceRegistryDao" p:connectionFactory-ref="servicePooledLdapConnectionFactory" p:searchRequest-ref="searchRequest" p:ldapServiceMapper-ref="ldapMapper" /> <bean id="servicePooledLdapConnectionFactory" class="org.ldaptive.pool.PooledConnectionFactory" p:connectionPool-ref="serviceConnectionPool" /> <bean id="serviceConnectionPool" parent="abstractConnectionPool" p:connectionFactory-ref="serviceConnectionFactory" /> <bean id="serviceConnectionFactory" class="org.ldaptive.DefaultConnectionFactory" p:connectionConfig-ref="serviceConnectionConfig" /> <bean id="serviceConnectionConfig" parent="svcAbstractConnectionConfig" p:connectionInitializer-ref="serviceConnectionInitializer" /> <bean id="svcAbstractConnectionConfig" abstract="true" class="org.ldaptive.ConnectionConfig" p:ldapUrl="${ldap.service.url}" p:connectTimeout="${ldap.connectTimeout}" p:useStartTLS="${ldap.useStartTLS}" p:sslConfig-ref="sslConfig" /> <bean id="serviceConnectionInitializer" class="org.ldaptive.BindConnectionInitializer" p:bindDn="${ldap.service.managerDn}"> <property name="bindCredential"> <bean class="org.ldaptive.Credential" c:password="${ldap.service.managerPassword}" /> </property> </bean> <bean id="searchRequest" class="org.ldaptive.SearchRequest" p:baseDn="${ldap.service.baseDn}" p:searchFilter="${ldap.service.searchFilter}" /> <bean id="ldapMapper" class="org.jasig.cas.adaptors.ldap.services.DefaultLdapServiceMapper"/> <!-- End of Serivce registry additions. --> <bean id="auditTrailManager" class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" /> <bean id="healthCheckMonitor" class="org.jasig.cas.monitor.HealthCheckMonitor" p:monitors-ref="monitorsList" /> <util:list id="monitorsList"> <bean class="org.jasig.cas.monitor.MemoryMonitor" p:freeMemoryWarnThreshold="10" /> <!-- NOTE The following ticket registries support SessionMonitor: * DefaultTicketRegistry * JpaTicketRegistry Remove this monitor if you use an unsupported registry. --> <!-- <bean class="org.jasig.cas.monitor.SessionMonitor" p:ticketRegistry-ref="ticketRegistry" p:serviceTicketCountWarnThreshold="5000" p:sessionCountWarnThreshold="100000" /> --> </util:list> </beans> This all being said, we still don't seem to be seeing anything but the user ID being returned to services even when we explicitly release them in the service definition in the ldap. We DO see those variable being searched for and returned in our ldap logs, so the authentication manager is grabbing them (and returning them to our Google SAML handler), but they do not seem to be properly stored in the attributeRepository fields. -- -- 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-user
