Whoops, That makes sense. For some reason, I'm still seeing the problem though. I've uncommented this from my pom.xml
<!-- Generic AuthN --> <dependency> <groupId>org.jasig.cas</groupId> <artifactId>cas-server-support-generic</artifactId> <version>${cas.version}</version> <type>jar</type> <scope>runtime</scope> </dependency> But after redeploying, I'm still hitting this exception: Cannot find class [org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler] for bean with name 'org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler#24c6e1ec' defined in ServletContext resource [/WEB-INF/deployerConfigContext.xml]; nested exception is java.lang.ClassNotFoundException: org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler Aloha, -baron On Thu, Sep 04, 2014 at 11:26:31PM -0700, Misagh Moayyed wrote: >> I'm not sure why I'm getting class not found. > >Because the handler you are using is not declared and found by your maven >pom. The handler exists in the cas-server-support-generic module, which >likely, you are missing. Add it back to the pom as a runtime dependency >and redeploy. > >-----Original Message----- >From: Baron Fujimoto [mailto:ba...@hawaii.edu] >Sent: Thursday, September 4, 2014 12:16 PM >To: cas-user@lists.jasig.org >Subject: Re: [cas-user] SimpleTest...AuthenticationHandler & Service >Management authorization > >Hmm, that's an idea, but I'm not sure it will meet their needs, since I >think they may want the principal of an actual user. I'll have to check. > >For the sake of testing this though, I tried it out but ran into a >problem. > >When I uncomment the sample in deployerConfigContext.xml before >BindLdapAuthenticationHandler: > > <bean >class="org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler"> > <property name="users"> > <map> > <entry> > <key> > <value>foo</value> > </key> > <value>bar</value> > </entry> > </map> > </property> > </bean> > >I get the following error when I deploy: > >2014-09-04 08:51:52,378 ERROR >[org.springframework.web.context.ContextLoader] - <Context initialization >failed> [...] Cannot find class >[org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler] for bean >with name >'org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler#923288b' >defined in ServletContext resource [/WEB-INF/deployerConfigContext.xml]; >nested exception is java.lang.ClassNotFoundException: >org.jasig.cas.adaptors.generic.AcceptUsersAuthenticationHandler > >I'm not sure why I'm getting class not found. > >-baron > >On Wed, Sep 03, 2014 at 11:53:32PM -0700, Misagh Moayyed wrote: >>It would be better, if instead of the simple-test handler you >>configured a set of users accepted by the accept-users handler. >>Configure the usernames to be something that could never exist in AD, and >put the handler first. >>Then have the management app to authorize accounts based on ldap, >>rather than a hardcoded set of users. >> >>-----Original Message----- >>From: Baron Fujimoto [mailto:ba...@hawaii.edu] >>Sent: Wednesday, September 3, 2014 7:15 PM >>To: cas-user@lists.jasig.org >>Subject: [cas-user] SimpleTest...AuthenticationHandler & Service >>Management authorization >> >>We'd like to provide some of our developers with the functionality >>available of the SimpleTestUsernamePasswordAuthenticationHandler. >> >>Is there a way to enable this, yet still require a more restrictive >>authentication handler for the users authorized to use the Services >>Management application? Ideally for example, the Services Management >>app would only be available to its enumerated users if they >>authenticate with the BindLdapAuthenticationHandler. Happy to RTFM if >>pointed to the appropriate link in TFM. We're using 3.4.11. >> >>Aloha, >>-baron -- Baron Fujimoto <ba...@hawaii.edu> :: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum desendus pantorum -- 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