Got the same using fastbind

2013-06-28 16:14:00,650 INFO [org.ldaptive.auth.Authenticator] - Authentication 
succeeded for dn: [email protected]
2013-06-28 16:14:00,651 DEBUG [org.ldaptive.auth.Authenticator] - authenticate 
response=[org.ldaptive.auth.AuthenticationHandlerResponse@867519822::connection=[org.ldaptive.DefaultConnectionFactory$DefaultConnection@598030336::config=[org.ldaptive.ConnectionConfig@468496818::ldapUrl=ldap://server150.samford.edu,
 connectTimeout=3000, responseTimeout=-1, sslConfig=null, useSSL=false, 
useStartTLS=false, 
connectionInitializer=org.ldaptive.ad.extended.FastBindOperation$FastBindConnectionInitializer@50862b70],
 
providerConnectionFactory=[org.ldaptive.provider.jndi.JndiConnectionFactory@872389192::connectionCount=1,
 environment={java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory}, 
providerConfig=[org.ldaptive.provider.jndi.JndiProviderConfig@241028931::operationExceptionResultCodes=[PROTOCOL_ERROR,
 SERVER_DOWN], properties={}, connectionStrategy=DEFAULT, 
environment={java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory}, 
tracePackets=null, removeDnUrls=true, 
searchIgnoreResultCodes=[TIME_LIMIT_EXCEEDED, SIZE_LIMIT_EXCEEDED, 
PARTIAL_RESULTS], sslSocketFactory=null, hostnameVerifier=null, 
controlProcessor=org.ldaptive.provider.ControlProcessor@30d23f13]], 
providerConnection=org.ldaptive.provider.jndi.JndiConnection@51ea07a3], 
result=true, resultCode=SUCCESS, message=null, controls=null] for 
[email protected] with 
request=[org.ldaptive.auth.AuthenticationRequest@970862244::user=jmdanner, 
retAttrs=null]
2013-06-28 16:14:00,651 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - LDAP response: 
[org.ldaptive.auth.AuthenticationResponse@676467183::authenticationResultCode=AUTHENTICATION_HANDLER_SUCCESS,
 ldapEntry=[[email protected][]], accountState=null, result=true, 
resultCode=SUCCESS, message=null, controls=null]
2013-06-28 16:14:00,652 INFO 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - 
LdapAuthenticationHandler failed authenticating jmdanner+password
2013-06-28 16:14:00,654 INFO 
[com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - Audit trail 
record BEGIN
=============================================================
WHO: audit:unknown
WHAT: supplied credentials: [jmdanner+password]
ACTION: AUTHENTICATION_FAILED
APPLICATION: CAS
WHEN: Fri Jun 28 16:14:00 CDT 2013
CLIENT IP ADDRESS: 199.20.16.38
SERVER IP ADDRESS: unknown
=============================================================

Mearl Danner
Systems Programmer
Samford University Technology Services
http://www.samford.edu

-----Original Message-----
From: Marvin S. Addison [mailto:[email protected]] 
Sent: Friday, June 28, 2013 3:14 PM
To: [email protected]
Subject: Re: [cas-dev] ldaptive integration

> I've attached my cas.log and my deployerConfig.xml

Logs look suspect -- may be a bug. I'll have to review more carefully 
Monday and possibly do some testing against our AD infrastructure. I'll 
update this thread when I have more info.

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-dev



-- 
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-dev

Reply via email to