Can you try setting SOGoCASLogoutEnabled = YES; and see if it does what it should?

We already try this.
When you click on the "logout button" you will by logout from SOGo and from CAS but you will not be log out for other application that you have a open session.

Exemple

You log in with cas
you open session in application A
you open session in SOGo
...
You logout from SOGo
You will be logout from CAS
Session in application A is always open... :-(

=====

With Single Sign Out

You log in with cas
you open session in application A
you open session in SOGo
...
You Single Sign Out from SOGo
You will be logout from CAS
CAS Server will call "logout" function for every application you open
In this case CAS Server will call logout from application A

I hope my explication is quite enought.

Best regards,
Ludovic.

Unless I'm mistaken, when you click the logout button in sogo, it will end up calling SOGoCASServiceURL/logout. The CAS server should then destroy the client's single sign-on CAS session and it will then do a POST to every registered services. The services should handle this POST and do any cleanup action required to logout the user correctly.

Can you verify that the above scenario is happening in your environment? When you click 'logout' application A should receive the POST request. If it doesn't, the cas logs might have some clue on why it isn't happening.

For SOGo it's should be ok, but when you logout from application A, you will be logout from CAS BUT NOT Logout from SOGo

For each application we have to tell them that i am "compatible" with the Single Sign Out ( Exemple in PHP : https://github.com/Jasig/phpCAS/blob/master/docs/examples/example_logout.php )

And i don't think there is a "handleLogoutRequests" for SOGo in the CAS process login.

This should be fixed with this commit: https://github.com/inverse-inc/sogo/commit/41ed498d6512b9cf2ef01654ea29be4c535d0c16

I'll close the ticket, if it still doesn't work for you, please reopen.