can't deploy service-management 4.2.3

[Chao]

Hi. I have set my cas server and it works fine and I want to deploy cas-management webapp. I built the app using maven successfully and copied etc folder to /etc/cas as the docs said.
But the war file cannot be deployed and below is the log:

2016-07-24 11:06:20,204 WARN [org.springframework.web.context.support.XmlWebApplicationContext] - <Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'assertionAsReturnValuePrincipalResolver' defined in URL [jar:file:/var/lib/tomcat7/webapps/cas-services/WEB-INF/lib/cas-server-core-audit-4.2.3.jar!/org/jasig/cas/audit/spi/AssertionAsReturnValuePrincipalResolver.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.jasig.cas.audit.spi.TicketOrCredentialPrincipalResolver]: : No qualifying bean of type [org.jasig.cas.audit.spi.TicketOrCredentialPrincipalResolver] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=auditablePrincipalResolver)}; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [org.jasig.cas.audit.spi.TicketOrCredentialPrincipalResolver] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=auditablePrincipalResolver)}>
2016-07-24 11:06:20,214 WARN [org.jasig.cas.services.JsonServiceRegistryConfigWatcher] - <Directory key is no longer valid. Quitting watcher service>
2016-07-24 11:06:20,221 ERROR [org.springframework.web.context.ContextLoader] - <Context initialization failed>

is there a jar missing or something? what should I do?!

[Chao]

I just deployed cas management webapp 4.2.2 and it worked
I think there's a problem with 4.2.3 you guys may check