So, you have modified "cas-server-3.1.1\cas-server-webapp\pom.xml" to
include the following lines after the cas-server-core dependency?
<dependency>
<groupId>org.jasig.cas</groupId>
<artifactId>cas-server-support-ldap</artifactId>
<version>${project.version}</version>
</dependency>
Then you stopped tomcat on the server, and removed
/var/lib/tomcat5/webapps/cas.war and /var/lib/tomcat5/webapps/cas/ (you
might have to blow away the contents of
/var/cache/tomcat5/work/Catalina/localhost/ as well)
Then you have built the thing using maven and copied the war file from
"cas-server-3.1.1\cas-server-webapp\target\cas.war" to
/var/lib/tomcat5/webapps
Then you restarted tomcat and it still doesn't work?
Is the cas-server-support-ldap-3.1.1.jar file in
/var/lib/tomcat5/webapps/cas/WEB-INF/lib? If it is there after all the
above, then the only other possibility that recommends itself to me is a
missing dependency for
org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource...
-- Dale
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jonathan Hayward http://JonathansCorner.com
Sent: Wednesday, 5 December 2007 10:22 a.m.
To: Yale CAS mailing list
Subject: Re: Username/password authentication
It built, but when I run it, I got the same error as before:
CAS is Unavailable
There was a fatal error initializing the CAS application context. This
is almost always because of an error in the Spring bean configuration
files. Are the files valid XML? Do the beans they refer to all exist?
Before placing CAS in production, you should change this page to present
a UI appropriate for the case where the CAS web application is
fundamentally broken. Perhaps "Sorry, CAS is currently unavailable."
with some links to your user support information.
The Throwable encountered at context listener initialization was:
org.springframework.beans.factory.BeanDefinitionStoreException: Error
registering bean with name 'contextSource' defined in ServletContext
resource [/WEB-INF/deployerConfigContext.xml]: Bean class
[org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource] not
found; nested exception is java.lang.ClassNotFoundException:
org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource
The Throwable encountered at dispatcher servlet initialization was:
org.springframework.beans.factory.BeanDefinitionStoreException: Error
registering bean with name 'contextSource' defined in ServletContext
resource [/WEB-INF/deployerConfigContext.xml]: Bean class
[org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource] not
found; nested exception is java.lang.ClassNotFoundException:
org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource
The comment Dave gave when I posted this message earlier was:
The missing class will be defined in cas-server-support-ldap. Adding
this dependency to the webapp pom.xml should include it in the built
cas.jar
- <dependency>
<groupId> org.jasig.cas</groupId>
<artifactId> cas-server-support-ldap</artifactId>
<version> ${project.version}</version>
</dependency>
Or, as a quick fix you could copy cas-server-support-ldap-3.1.1.jar to
the cas WEB-INF/lib directory on the app server.
While working on this message, I also tried the copy suggested in the
last line, bounced the server, and got the same message on trying to
login to CAS.
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
