Code review shows two ways the attribute map could be null, only one of which is likely. The culprit is line 168 in LdapPersonAttributeDao:
return (Map<String, List<Object>>)DataAccessUtils.uniqueResult(results); According to http://static.springframework.org/spring/docs/2.0.x/api/org/springframework/dao/support/DataAccessUtils.html#uniqueResult(java.util.Collection), that method will return null if the result set is empty, meaning your LDAP query returned 0 results. That is a pefectly valid search result, but one I would imagine you would encounter every time with two non-overlapping search scopes. The user is either in one place or another; so you should see the NPE every time. In that view, it's not surprising you discovered this bug. We clearly need to test for a null return value and handle it gracefully. I'll open a Jira issue for this against 3.3.2. 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
