Arkady,
These cas loggers may provide some additional information
<!-- DEBUG outbound and inbound headers and response -->
<AsyncLogger name="org.apache.http.headers" level="warn" />
<!-- DEBUG outbound and inbound headers and response as it is sent -->
<AsyncLogger name="org.apache.http.wire" level="warn" />
Ray
On Mon, 2022-06-27 at 00:52 -0700, Arkady Keppert wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
I set up the CAS 6.5.2 cluster based on:
https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html
Everything works nicely outside of the SAML2 SOL services, if I log out of the
SAML2 service then the ticket is nicely destroyed and im logged out from all
applications, but if I log out of my other services I get the information that:
CAS.log
2022-06-27 09: 34: 21,784 WARN
[org.apereo.cas.support.saml.web.idp.profile.slo.SamlIdPSingleLogoutServiceMessageHandler]
- <No (successful) logout response received from the url [https: // sp
.uek.krakow.pl / Shibboleth.sso / SLO / POST]>
2022-06-27 09: 34: 21,784 WARN
[org.apereo.cas.logout.slo.BaseSingleLogoutServiceMessageHandler] - <Logout
message is not sent to [AbstractWebApplicationService (id = https:
//sp.uek.krakow.pl/shibboleth , originalUrl = https:
//sp.uek.krakow.pl/shibboleth, artifactId = null, principal = kepperta, source
= service, loggedOutAlready = false, format = XML, attributes = {entityId =
[https: //sp.uek .krakow.pl / shibboleth]})]; Continuing processing ...>
SAML SP log:
2022-06-27 03:34:21 INFO Shibboleth.Logout.SAML2 [11] [default]: processing
front channel logout request with no active session
2022-06-27 03:34:21 INFO Shibboleth.SessionCache [11] [default]: request to
logout sessions from (https://sso-test.uek.krakow.pl/cas/idp) for (kepperta)
2022-06-27 03:34:21 INFO Shibboleth.Logout.SAML2 [11] [default]: client's
session isn't available, skipping front-channel notifications
2022-06-27 03:34:21 ERROR Shibboleth.Logout [11] [default]: no sessions
supplied to back channel notification method
When logging in to Shibboleth, a session is created that CAS knows nothing
about and when logging out of another service, this session is not transferred
to SAML SP, as I wrote earlier, if you logout directly in Shibboleth then SOL
works and I am logged out of other services. I tested it on my SAML SP and via
the website: https://samltest.id/ or both solutions are based on Shibboleth
Has anyone had similar problems and knows how to solve it?
--
- 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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/3eb80783a836f14868f30f369de19adbdae533a6.camel%40uvic.ca.
