After looking through all the config files again, I realized I had failed to un-comment a portion relating to the Active Directory in the passwordManagerContext.xml file, so I made those portions available and built the package again.
However, now the application will not start, and catalina.out displays an errors about being unable to resolve a placeholder for password.warn.days: *org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'ldapServer' defined in ServletContext resource [/WEB-INF/spring-configuration/passwordManagerContext.xml]: Could not resolve placeholder 'pm.ldap.server.ad.password.warn.days'* I have in fact set the attribute for password warn days (though the correct attribute may be wrong) in the cas.properties file, so I'm a little lost. *Server info:* Red Hat Enterprise Linux Server release 6.0 (Santiago) CAS Version 3.5 Maven 3 Tomcat7 *I'm attempting to follow the instructions found at:* https://github.com/Unicon/cas-password-manager *The full error message (from catalina.out) is below:* 2014-05-28 09:33:05,705 ERROR [org.jasig.cas.web.init.SafeContextLoaderListener] - <SafeContextLoaderListener: The Spring ContextLoaderListener we wrap threw on contextInitialized. But for our having caught this error, the web application context would not have initialized.> org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'ldapServer' defined in ServletContext resource [/WEB-INF/spring-configuration/passwordManagerContext.xml]: Could not resolve placeholder 'pm.ldap.server.ad.password.warn.days' at org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:209) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:220) at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:84) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:681) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:656) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:446) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:385) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111) at org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized_aroundBody0(SafeContextLoaderListener.java:75) at org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized_aroundBody1$advice(SafeContextLoaderListener.java:57) at org.jasig.cas.web.init.SafeContextLoaderListener.contextInitialized(SafeContextLoaderListener.java:1) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4973) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:670) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) On Tue, May 27, 2014 at 10:04 AM, Misagh Moayyed <mmoay...@unicon.net>wrote: > If you are just trying to log into CAS, and not to any other application > (basically meaning the service parameter to the CAS login endpoint is left > out), you can safely ignore the messages you see in the logs about argument > extractors. > > > > Now, the “credentials bad” issue is a different story. If you have hooked > up CAS to AD, and you don’t see any other errors, stack traces or anything > else like that in the logs, changes are CAS can simply not find you in the > location configured inside AD. Check credentials, base path, etc…make sure > the password is correct, and make sure the test account isn’t locked etc. > > > > …and what CAS version are you testing? > > > > If none of that is any help, do please post/attach the log here where you > see the “credentials bad” error > > > > *From:* Mike Seiler [mailto:michaelsei...@fuller.edu] > *Sent:* Tuesday, May 27, 2014 9:58 AM > *To:* cas-user@lists.jasig.org > *Subject:* Re: [cas-user] Extractor Errors after Install > > > > Misagh, > > > > I am using CAS with Active Directory. We are trying to implement a CAS > Password Manager that I found on GitHub. So far I've been able to confirm > that the Certificates are appropriately installed, and that CAS can speak > with the AD server. > > > > When these messages occur, I am attempting to log in as my test user, > which returns a "credentials bad" note in the cas.log, as well as these > Extractor messages. However, command line searches using my test user's > username and password return valid results from AD, so I know that the > credentials are valid. > > > > If CAS is unable to parse the response, then I suppose that this is > causing the "credentials bad" message? > > > > Thanks, > > > > Mike > > > > On Tue, May 27, 2014 at 9:38 AM, Misagh Moayyed <mmoay...@unicon.net> > wrote: > > These are not errors, per se. These are simply informational messages > logged at the DEBUG level. What they indicate is that CAS is unable to > parse the incoming request. How are you accessing the CAS server and what > are you trying to accomplish? > > > > *From:* Mike Seiler [mailto:michaelsei...@fuller.edu] > *Sent:* Tuesday, May 27, 2014 9:10 AM > *To:* cas-user@lists.jasig.org > *Subject:* [cas-user] Extractor Errors after Install > > > > Hello all, > > > > I just installed CAS, and it seems everything was set up properly, but I > keep receiving the following errors: > > > > 2014-05-23 14:45:25,894 DEBUG > [org.jasig.cas.web.support.CasArgumentExtractor] - Extractor did not > generate service. > > 2014-05-23 14:45:25,894 DEBUG > [org.jasig.cas.web.support.SamlArgumentExtractor] - Extractor did not > generate service. > > > > My Google searches have not resulted in an answer that solves this. Does > anyone have some insight? > > > > Thanks, > > > > Mike > > > > -- > > *Michael Seiler* > > -------------------------------------------------- > > Systems Integration Engineer > > Fuller Theological Seminary > > Phone: (970) 306-6105 > > michaelsei...@fuller.edu > > > > *Please NOTE:* > I respond to email at 8 AM, 1PM, and at 4:30PM. If you need more > immediate help, please contact TSS (626.584.5675) and they can route the > issue to the appropriate person. If this is a business process life or > death emergency, you may call me at the above number. > > > > -- > > You are currently subscribed to cas-user@lists.jasig.org as: > mmoay...@unicon.net > > 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: > michaelsei...@fuller.edu > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > > > > -- > > *Michael Seiler* > > -------------------------------------------------- > > Systems Integration Engineer > > Fuller Theological Seminary > > Phone: (970) 306-6105 > > michaelsei...@fuller.edu > > > > *Please NOTE:* > I respond to email at 8 AM, 1PM, and at 4:30PM. If you need more > immediate help, please contact TSS (626.584.5675) and they can route the > issue to the appropriate person. If this is a business process life or > death emergency, you may call me at the above number. > > > > -- > > You are currently subscribed to cas-user@lists.jasig.org as: > mmoay...@unicon.net > > 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: > michaelsei...@fuller.edu > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- *Michael Seiler* -------------------------------------------------- Systems Integration Engineer Fuller Theological Seminary Phone: (970) 306-6105 michaelsei...@fuller.edu *Please NOTE:* I respond to email at 8 AM, 1PM, and at 4:30PM. If you need more immediate help, please contact TSS (626.584.5675) and they can route the issue to the appropriate person. If this is a business process life or death emergency, you may call me at the above number. -- 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
