Can't get FRONT_CHANNEL SLO to happen

[Jez P]

Hi everyone, 

This is probably because I've missed something in the documentation but working with a local CAS server (purely for testing a pac4j implementation) I can create a service using the json local file approach (purely because I want minimal moving parts) and I can make back channel logout work with the following JSON descriptor for the service:-

{

  "@class" : "org.apereo.cas.services.RegexRegisteredService",

  "serviceId" : "^http://.*",

  "name" : "testJsonFile",

  "id" : 103935657744185,

  "evaluationOrder" : 10,

  "logoutType" : "BACK_CHANNEL",

  "logoutUrl" : "http://localhost:8080/callback?client_name=CasClient"

}

It can be seen in the debug-level logging when I log out (by going to the cas login page and choosing logout) that indeed we are using BACK_CHANNEL

2017-08-04 21:11:28,670 DEBUG [org.apereo.cas.logout.DefaultSingleLogoutServiceMessageHandler] - <Logout type registered for [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@246395ab[id=http://localhost:8080/callback?client_name=CasClient,originalUrl=http://localhost:8080/callback?client_name=CasClient,artifactId=<null>,principal=jprime,loggedOutAlready=true,format=XML]] is [BACK_CHANNEL]>

and I see the callback to my application result in the user being logged out. Perfection. 

So far so good. However, if in the above descriptor I replace BACK_CHANNEL with FRONT_CHANNEL (and no other changes) and restart (though AIUI that shouldn't be necessary) I would expect now when I do the same thing that rather than a POST to my application, I should see a redirect of the browser and something in the log that says we are now using FRONT_CHANNEL. Instead I see the same behaviour as before, and the same log entry

2017-08-04 21:17:00,986 DEBUG [org.apereo.cas.logout.DefaultSingleLogoutServiceMessageHandler] - <Logout type registered for [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@38eb62e3[id=http://localhost:8080/callback?client_name=CasClient,originalUrl=http://localhost:8080/callback?client_name=CasClient,artifactId=<null>,principal=jprime,loggedOutAlready=true,format=XML]] is [BACK_CHANNEL]>

Is there some additional piece of configuration I need to put in place to enable experimental front channel logout?

The CAS server I'm using is basically the overlay from https://github.com/apereo/cas-overlay-template (push) with very minor config tweaks. So there's got to be something I'm missing, because I can't find others experiencing this problem.

Please could someone let me know if you see what I'm doing wrong?

[Jozef Kotlar - EEA.sk]

Hello,

I am struggling with same behaviour and it seems to me, that logoutType settings is ignored and defaulting to BACK_CHANNEL.

[jez prime]

I'm glad it's not just me. I've given up on this, only wanted to be able to satisfy myself that vertx-pac4j's front channel logout support worked (back channel certainly does). I'll assume it does and when someone with a valid config raises an issue about it, I'll follow up then. Trying to configure it for CAS has wasted enough of my time. I also tried through the DB services approach, but that just started spitting out weird exceptions (the limited documentation really doesn't help).

On Monday, September 4, 2017 at 4:18:52 PM UTC+1, Jozef Kotlar - EEA.sk wrote:

Hello,

I am struggling with same behaviour and it seems to me, that logoutType settings is ignored and defaulting to BACK_CHANNEL.

--
- 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+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/f27a69c0-23c9-4010-896d-f5d27e3e24bb%40apereo.org.

[SOPHIE Fang]

Same here

在 2017年9月4日星期一 UTC-4上午11:18:51，Jozef Kotlar - EEA.sk写道：

[Jozef Kotlár]

Hello,

this is solved already in 5.2.0-RC4 - https://github.com/apereo/cas/pull/2909

Jozef

--

- 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 a topic in the Google Groups "CAS Community" group.
To unsubscribe from this topic, visit https://groups.google.com/a/apereo.org/d/topic/cas-user/WfGdbIuXSx0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cas-user+unsubscribe@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/96794c4d-9443-4013-b2bd-7cb58253128f%40apereo.org.

[Jez P]

Wow - thanks very much Jozef. I will have another bash at my testing for vertx-pac4j with front logout over the weekend and will feed back to you if I run into problems.

Cheers,

Jez

On Wednesday, October 18, 2017 at 9:16:47 AM UTC+1, Jozef Kotlar - EEA.sk wrote:

Hello,

this is solved already in 5.2.0-RC4 - https://github.com/apereo/cas/pull/2909

Jozef

On Tue, Oct 17, 2017 at 8:56 PM, SOPHIE Fang <sophie....@gmail.com> wrote:

Same here

在 2017年9月4日星期一 UTC-4上午11:18:51，Jozef Kotlar - EEA.sk写道：

Hello,

I am struggling with same behaviour and it seems to me, that logoutType settings is ignored and defaulting to BACK_CHANNEL.

--
- 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 a topic in the Google Groups "CAS Community" group.
To unsubscribe from this topic, visit https://groups.google.com/a/apereo.org/d/topic/cas-user/WfGdbIuXSx0/unsubscribe.

To unsubscribe from this group and all its topics, send an email to cas-user+u...@apereo.org.