Cas5.3.0 Zì dìngyì dēnglù rènzhèng 15/5000 Cas5.3.0 custom login authentication

[李雁敏]

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.

[Ray Bon]

What are your customizations?

What is in the debug logs?

Ray

On Fri, 2019-05-17 at 01:36 -0700, 李雁敏 wrote:

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.

-- 

Ray Bon

Programmer Analyst

Development Services, University Systems

2507218831 | CLE 019 | rb...@uvic.ca

[李雁敏]

Is a user database authentication and query

在 2019年5月17日星期五 UTC+8下午4:36:53，李雁敏写道：

[Andy Ng]

Dear Lee,

Seeing your log, I suspect you are using http instead of https for your CAS server, 

CAS SSO do not work with https, if you are not using https, please configure CAS to use https

Cheers!

- Andy

[Andy Ng]

* CAS SSO do not work without https

[李雁敏]

Hello, I have configured the https protocol locally, but I can't implement SSO in the https protocol. I developed it in the intranet environment.

在 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.

[李雁敏]

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.

[Ray Bon]

Increase logging level to debug.

What log in handler do you have configured?

Ray

[李雁敏]

Yes, I customized the login process. I failed to inject @Bean when using custom login. I have already solved it, thank you very much.

在 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.

[李雁敏]

In the process of use, I found that version 5.3.0 can not achieve single sign-on, I replaced the 5.3.9 version to solve, and also tried a lot of ways to find a solution, can not make the 5.3.0 version of cas Single sign-on, why is this?

Now the problem is solved, but I don't quite understand why 5.3.0 can't implement single sign-on.

在 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.