On Jul 24, 2014, at 9:12 AM, Raymond Drew Walker <[email protected]> wrote: > After turning up TRACE on org.ldaptive.control I only saw one extra log > pertaining to decoding control: ... > connection=[org.ldaptive.DefaultConnectionFactory$DefaultConnection@1666623 > 515::config=[org.ldaptive.ConnectionConfig@1511332517::ldapUrl=ldap://ldap- > dev.nau.edu, connectTimeout=3000, responseTimeout=-1, sslConfig=null, > useSSL=false, useStartTLS=false, connectionInitializer=null], .. > providerConfig=[org.ldaptive.provider.jndi.JndiProviderConfig@163575813::op > erationExceptionResultCodes=[PROTOCOL_ERROR, SERVER_DOWN], properties={}, > connectionStrategy=DEFAULT, environment=null, tracePackets=null, > removeDnUrls=true, searchIgnoreResultCodes=[TIME_LIMIT_EXCEEDED, > SIZE_LIMIT_EXCEEDED, PARTIAL_RESULTS], sslSocketFactory=null, > hostnameVerifier=null, > controlProcessor=org.ldaptive.provider.ControlProcessor@1a341543]], > providerConnection=org.ldaptive.provider.jndi.JndiConnection@515fef25]>
Since both SSL and StartTLS are false, are you certain your LDAP server isn't simply refusing to perform these operations over an insecure connection? Tom. -- 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
