My goal, if possible is to ignore and not chase referrals if at all possible.
I must admit we don't provide very good referral handling. Typically you want to discard referrals and not even include them in the result set. Unfortunately that is not possible via JNDI environment parameters or via Spring LDAP. The ignorePartialResultException flag simply causes the PartialResultException to be swallowed when it occurs on reading the _first_ referral result out of a NamingEnumeration; it's the behavior that's closest to ignoring referrals altogether. But it's not the same. You have to assume that referrals come _after_ meaningful results, which is safe in practice but certainly not guaranteed by either Microsoft or the LDAP protocol. Under that assumption dropping referrals is the same as ignoring the exception, but it's worth noting the assumption because it may not hold in all cases.
Setting p:ignorePartialResultException="false" on the context source used for the search operation should be sufficient. Post your BindLdapAuthenticationHandler bean config, logs at DEBUG, and stack trace if you continue to have trouble.
Is there a filter of some sort I can use? Something different I can do when searching?
Search the GC, as recommended earlier. It doesn't return referrals. 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
