> The problem with catching 2.16.840.1.113730.3.4.4 is that, this is not error > code at all, but a result of search after binding - I can't use here LDAP > policy enforcement at LDAP server stage.
Can you confirm exactly what it is? It appears to be a response control OID, but I'm not familiar with RHDS at all. I can say that if it is, in fact, a response control, then it's not looking good. I'm not aware of any facility whatever in Spring LDAP for accessing response controls. It's worth noting that the ldaptive library has a facility for obtaining response controls; I have proposed migrating to ldaptive for CAS LDAP integration, and this may be a relevant use case. 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
