> I changed my CAS server to point at an Active Directory server (which I > really don’t much about) and now I can’t authenticate.
Authentication problems that appear related to bad credentials are best diagnosed in the authentication provider logs, which is AD in this case. I'd recommend working with your AD admin to get some good logs that indicate the problem. > I am a bit confused how to config log4j to up the number of messages because > of these seemingly contradictory comments: I'll try to clear up your confusion since understanding how to turn up CAS server logging is very helpful. JBoss can be made to support application-controlled logging, but it is difficult and would require customizations to JBoss core logging components. Practically speaking it's not supported. The Spring org.springframework.web.util.Log4jConfigListener component is for simple servlet containers like Tomcat and Jetty that allow the application to control logging, which as I said is not supported by JBoss. So it's strongly recommend that it be commented out/removed for JBoss. The comment in the log4j.properties file is consistent with JBoss's strategy of container-controlled logging instead of application-controlled. The JBoss container log config file, $JBOSS_HOME/server/default/deploy/log4j.xml, is where logging configuration should happen on JBoss, not in the log4j.properties file deployed with the WAR file. On a typical servlet container like Tomcat, you should enable the Log4jConfigListener in web.xml which will cause the log4j.properties file cas.war deployable to be read and monitored for changes. All logging configuration should be handled in log4j.properties. Does that clear up your confusion? 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-user
