Hi Andrew,
Thanks so much, now I understand a bit more what I’m doing (even a few is still
appreciable).
In fact, the bean was in the deployer but inside an another one.
ð <bean id="auditTrailManager"
class="com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager" >
<bean id="contextSource"
class="org.springframework.ldap.core.support.LdapContextSource">
<property name="pooled" value="false"/>
<property name="url"
value="ldap://192.168.190.5:389"; />
<property name="userDn" value="cn=cas.user"/>
<property name="password" value="P@ssword"/>
<property name="baseEnvironmentProperties">
<map>
<entry
key="com.sun.jndi.ldap.connect.timeout" value="3000" />
<entry
key="com.sun.jndi.ldap.read.timeout" value="3000" />
<entry
key="java.naming.security.authentication" value="simple" />
</map>
</property>
</bean>
ð </bean>
I moved it outside and it worked. No more deploying error and I access to CAS
by browser.
Really helpful your advice.
I’m now struggling with authentication on the LDAP, but that’s another topic.
I go fishing and post a new thread in case.
Thanks again to you and the community.
__________________________________________
Guillaume DEPINAY
Service Informatique
ENSAP Bordeaux
740 cours de la Libération
BP 70109 - 33405 Talence cedex
Tel : 33 (0) 5.57.35.11.43
Mel :
[email protected]<mailto:[email protected]>
Web : http://www.bordeaux.archi.fr<http://www.bordeaux.archi.fr/>
___________________________________________
--
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
