> The logs are attached. It's suspect that the last attribute query entry is the following:
[org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao] - Generated query builder '([email protected])' from query Map {username=[[email protected]]}. In the case of successful attribute release, you should see entries like the following: 2010-09-21 09:57:43,655 DEBUG [org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl] - Retrieved attributes='[NamedPersonImpl[name=username,attributes={accountState=[ACTIVE], authId=[username], Formatted Name=[username], groupMembership=[uugid=group1,ou=Groups,dc=vt,dc=edu, uugid=group2,ou=Groups,dc=vt,dc=edu, uugid=group3,ou=Groups,dc=vt,dc=edu], uid=[12345], UDC_IDENTIFIER=[7CF7812347C17395E0441234BA624FA9], virginiaTechAffiliation=[VT-EMPLOYEE-STATE, VT-EMPLOYEE, VT-ACTIVE-MEMBER, VT-STAFF, VT-STUDENT, VT-ALUM-CONSTITUENT, VT-ALUM, VT-ALUM-PARENT]}]]' for query='{username=[username]}', isFirstQuery=false, currentlyConsidering='org.jasig.services.persondir.support.ldap.ldappersonattribute...@569764bd', resultAttributes='null' Can you confirm that your LDAP query is valid and that you can execute it against your LDAP server using the same parameters as those defined in your deployerConfigContext.xml? I typically use ldapsearch, part of the ldap-utils package, for investigations like that. M -- 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
