When I am using custom login authentication, I can't log in. I check the log and found:
2019-05-27 10:14:06,596 INFO [org.apereo.cas.support.events.listener.DefaultCasEventListener] - <> 2019-05-27 10:14:06,599 INFO [org.apereo.cas.support.events.listener.DefaultCasEventListener] - <Ready to process requests @ [2019-05-27T02:14:06.573Z]> 2019-05-27 10:14:06,607 INFO [org.apereo.cas.web.CasWebApplicationServletInitializer] - <Started CasWebApplicationServletInitializer in 122.392 seconds (JVM running for 248.415)> [2019-05-27 10:14:06,966] Artifact cas-overlay:war: Artifact is deployed successfully [2019-05-27 10:14:06,966] Artifact cas-overlay:war: Deploy took 235,554 milliseconds 2019-05-27 10:14:08,574 INFO [org.apereo.cas.web.flow.login.InitialFlowSetupAction] - <Setting path for cookies for warn cookie generator to: [/cas/] > 2019-05-27 10:14:08,717 INFO [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN ============================================================= WHO: audit:unknown WHAT: [event=success,timestamp=Mon May 27 10:14:08 CST 2019,source=RankedAuthenticationProviderWebflowEventResolver] ACTION: AUTHENTICATION_EVENT_TRIGGERED APPLICATION: CAS WHEN: Mon May 27 10:14:08 CST 2019 CLIENT IP ADDRESS: 127.0.0.1 SERVER IP ADDRESS: 127.0.0.1 ============================================================= > 2019-05-27 10:14:17,410 INFO [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN ============================================================= WHO: audit:unknown WHAT: [event=success,timestamp=Mon May 27 10:14:17 CST 2019,source=RankedAuthenticationProviderWebflowEventResolver] ACTION: AUTHENTICATION_EVENT_TRIGGERED APPLICATION: CAS WHEN: Mon May 27 10:14:17 CST 2019 CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1 SERVER IP ADDRESS: 0:0:0:0:0:0:0:1 ============================================================= > 2019-05-27 10:14:26,568 INFO [org.apereo.cas.services.AbstractServicesManager] - <Loaded [2] service(s) from [InMemoryServiceRegistry].> 2019-05-27 10:14:28,593 ERROR [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - <Authentication has failed. Credentials may be incorrect or CAS cannot find authentication handler that supports [UsernamePasswordCredential(username=admin)] of type [UsernamePasswordCredential]. Examine the configuration to ensure a method of authentication is defined and analyze CAS logs at DEBUG level to trace the authentication event.> 2019-05-27 10:14:28,595 ERROR [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - <[CustomAuthenticationHandler]: []> 2019-05-27 10:14:28,637 INFO [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN ============================================================= WHO: admin WHAT: Supplied credentials: [UsernamePasswordCredential(username=admin)] ACTION: AUTHENTICATION_FAILED APPLICATION: CAS WHEN: Mon May 27 10:14:28 CST 2019 CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1 SERVER IP ADDRESS: 0:0:0:0:0:0:0:1 ============================================================= 在 2019年5月17日星期五 UTC+8下午4:36:53，李雁敏写道： > > In the cas, the authentication is customized, but after accessing the > custom login authentication, I found that when logging in multiple systems, > single sign-on is not possible. Please give me some suggestions. > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6ad900df-72db-4217-b7f3-f12c174bea8b%40apereo.org.
