Thanks Daniel, I enabled debug logging on the org.ldaptive package and figured out LDAP traffic was being blocked by an ACL on the network. I have that changed now and the app loads. Now I just need to figure out why the LDAP query itself is failing!
On Wed, Jun 11, 2014 at 9:17 PM, Daniel Fisher <[email protected]> wrote: > Define a logger for the org.ldaptive package to see why the pool > cannot open connections. > > http://jasig.github.io/cas/4.0.0/installation/Logging.html > > --Daniel Fisher > > On Wed, Jun 11, 2014 at 8:42 PM, Daniel Salzedo <[email protected]> > wrote: >> Thank you so much for the reply. Here is what I have done: >> >> Removed the reference to ldap.properties from propertyFileConfigurer.xml >> Hard-coded all the variable values I had in ldap.properties into >> deployerConfigContext.xml >> Set ldapPoolConfig property "validateOnCheckOut" to true, as otherwise it >> causes a "Validator configured, but no validate flag has been set" error >> Rebuilt the project >> >> Now I get a new error trying to create the bindConnectionPool bean: >> >> Caused by: org.springframework.beans.factory.BeanCreationException: Error >> creating bean with name 'bindConnectionPool' defined in ServletContext >> resource [/WEB-INF/deployerConfigContext.xml]: Invocation of init method >> failed; nested exception is java.lang.IllegalStateException: Could not >> initialize pool size >> >> >> I have attached the new deployerConfigContext.xml with the LDAP password >> redacted. Note I am not using LDAPS in the lab so I have set useStartTLS to >> false and have not defined an SSL certificate path. Any ideas what is >> causing this new error? >> >> Daniel. >> >> On Wednesday, June 11, 2014 5:00:09 PM UTC-7, David Ordas wrote: >>> >>> Hi, in fact that is a Spring missconfigured reason. >>> >>> If you interpret the exception message you could understand that there is >>> some bean with a property/setter called "path" that only accept values >>> prepended by classpah: or file: >>> >>> Maybe your new property configure location.... >>> >>> Best regards >>> >>> El 12/06/2014 01:42, "Daniel Salzedo" <[email protected]> escribió: >>>> >>>> I am building a CAS v4.0 server in a lab environment for the first >>>> time, so it is entirely possible I have made some very basic mistake >>>> somewhere. >>>> >>>> My setup is running Centos v5.10 with JDK v1.60. (I have to use these >>>> specific versions as part of the project specifications I was given.) >>>> I built the CAS applicationusing the Maven WAR overlay method and it >>>> will run OK using the basic configuration from >>>> >>>> https://raw.githubusercontent.com/Jasig/cas/v4.0.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml. >>>> >>>> I need trying to get an authenticated LDAP bind setup using the sample >>>> code at >>>> http://jasig.github.io/cas/4.0.0/installation/LDAP-Authentication.html. >>>> I have created an ldap.properties file and added it to the >>>> propertyFileConfigurer.xml file under >>>> $PROJECT_HOME/src/main/webapp/WEB-INF/spring-configuration and it >>>> deploys OK. The problem I am having is the bindConnectionPool bean >>>> will not create properly. This error comes up every time the app tries >>>> to start. I've Googled it and can find no references to this error >>>> anywhere: >>>> >>>> Caused by: org.springframework.beans.factory.BeanCreationException: >>>> Error creating bean with name 'bindConnectionPool' defined in >>>> ServletContext resource [/WEB-INF/deployerConfigContext.xml]: >>>> Invocation of init method failed; nested exception is >>>> java.lang.IllegalArgumentException: path must start with either >>>> classpath: or file: >>>> at >>>> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512) >>>> ...... >>>> Caused by: java.lang.IllegalArgumentException: path must start with >>>> either classpath: or file: >>>> at org.ldaptive.LdapUtils.getResource(LdapUtils.java:399) >>>> ... >>>> >>>> I've attached my deployerConfigContext.xml file. Please let me know if >>>> you have any suggestions on how to fix this, or what I am doing wrong >>>> that may be causing this. >>>> >>>> Thanks, >>>> Daniel. >>>> >>>> -- >>>> 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 >>> >>> -- >>> 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 >> >> -- >> 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 > > -- > 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 > -- 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
