Allo, Guillaume,
It seems that the issue is caused by the constructor-arg for the
authenticationManager bean, where you have:
<entry key-ref="proxyAuthenticationHandler"
value-ref="proxyPrincipalResolver" />
<entry key-ref="primaryAuthenticationHandler"
value-ref="primaryPrincipalResolver" />
<entry key-ref="ldapAuthenticationHandler"
value-ref="usernamePasswordCredentialsResolver" />
Your authentication attempt goes through the primaryAuthenticationHandler
and fails. Since you want to use LDAP, and already have the LDAP handler
there, simply comment out the entry for the primaryAuthenticationHandler
and the referenced beans (primaryAuthenticationHandler,
primaryPrincipalResolver). If you also want to use the same LDAP directory
for attribute resolution, change the value-ref for the
ldapAuthenticationHandler entry to "#{ null }" and comment out the
usernamePasswordCredentialsResolver bean.
Best regards,
--
Carlos.
-----Original Message-----
From: Guillaume Chéramy [mailto:guilla...@cheramy.name]
Sent: Thursday, 17 September, 2015 09:27
To: cas-user@lists.jasig.org
Subject: [cas-user] Aperao CAS 4.1.0-RC2 with LDAP backend : Invalid
Credential
Hello,
I'll test to install CAS 4 with LDAP backend for testing before
migration from CAS 3.4.
So I install CAS with simple-cas4-overlay adapted for LDAP. There is my
deployerConfigContext.xml in joint file.
All start well and I arrive on CAS login page. But when I put my login
(uid) and my password I have always a Invalid credentials but :
=> I can saw request to LDAP in logs
=> if I test a ldapsearch with the same user all is good
Where is my mistake ?
Thanks for you're help.
Sincerely
guidtz
--
You are currently subscribed to cas-user@lists.jasig.org as:
cfern...@sju.edu To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
