Thanks Marvin, I will solve the dependency problem first.
My custom handler is like the original
public boolean supports(final Credentials credentials) {
return credentials != null
&& X509CertificateCredentials.class.isAssignableFrom(credentials
.getClass());
}
I will see if the problem is the dependency.
Thanks
2010/2/22 Marvin Addison <[email protected]>
> It looks like you have some dependency problems that might be
> preventing one of your context files from loading:
>
> 2010-02-22 17:50:46,073 DEBUG
> [org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver]
> - Ignoring handler
> [org.springframework.scripting.config.LangNamespaceHandler]: problem
> with class file or dependent class
> java.lang.NoClassDefFoundError:
> org/codehaus/groovy/control/CompilationFailedException
>
> Apparently this is happening because you are using the Spring lang
> schema but you're missing the Groovy dependency. I would suggest
> fixing that problem first and see if your custom authentication
> handler fires.
>
> If you continue to have trouble, here are some other things to consider:
>
> - Make sure your custom X.509 auth handler specifically supports the
> X509CertificateCredentials credential type. Auth handlers are tested
> for support for a specific credential type and invoked only if the
> supports() method returns true for a particular credential.
> - Make sure your custom auth handler is registered in your
> AuthenticationManager bean.
>
> 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
>
--
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
