No, the SAML2 specs do include ("support", if you wish) single logout
so wherever you read that, you can easily see it's wrong by looking
at the SAML2 specs[1] yourself.
SimpleSAMLphp implements some of the bindings usable for that, but
AFAIK Google Apps do not support SAML2 logout, they simply redirect to
some URL you can configure (which is not the same as SAML2 single
logout).
-peter
[1] "4.4 Single Logout Profile" in
http://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf
and "3.7 Single Logout Protocol" in
http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf
both linked from http://saml.xml.org/saml-specifications
The problem is that Google Apps do not support SAML2 Single Logout.
If you hit logout in Google Apps, Google will kill it's own session and just do a "plain" redirect to the Logout endpoint, that you have specified in Google Apps control panel. So if you want logout to work with your SSP installation, you need to implement some additional logic yourself.
Regards / Med venlig hilsen
Jacob Christiansen
System Developer
WAYF
Phone/Tlf: +45 31313631
Mail: ja...@wayf.dk
Skype: jacchristiansen
H. C. Andersens Boulevard 2
DK-1553 København V
> --
> You received this message because you are subscribed to the Google Groups "simpleSAMLphp" group.
> To post to this group, send email to simple...@googlegroups.com.
> To unsubscribe from this group, send email to simplesamlph...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simplesamlphp?hl=en.
>
As Google does not support SAML logout if you wanted to disable the
session at your SSP IdP you'd need to do that yourself (don't know if
SSP offers any helper functions for that, it probably does).
But you could redirect to any resource on your IdP vhost you want and
simply put some simple code there that overwrite's any cookies that
match the cookie name your SSP IDP sets (and present whatever text you
see fit for the user).
Note that since this is not Single Logout if you accessed any other
SAML SP besides the one you just logged out from (Google Apps in this
case) you'll still be logged in there and logout of from Google Apps
and destroying your session cookie at the IDP will not change that.
So telling users they're logged out when in fact you cannot know
whether they really are is not doing them a favor, security-wise.
-peter
The simplest workaround is to point Google Apps to the IdP-initiated
single logout service endpoint. That will trigger a logout both at the
IdP and at all SPs the user is currently logged in to.
Unfortunately, if you are using the iframe logout handler, the Google
Apps SP will show up in the list of SPs that the IdP is attempting to
log the user out from. The logout will fail because there isn't a
SingleLogoutService endpoint registered for that SP.
To use the IdP initiated logout, point Google Apps to:
https://idp.example.org/simplesaml/saml2/idp/SingleLogoutService.php?ReturnTo=https://some.page
Regards,
Olav Morken
UNINETT / Feide