SLO problems

We have SSO working fine, but SLO is giving us trouble.
We get this error every time:

ComponentSpace.SAML2.Exceptions.SAMLProtocolException: There is no SSO session to partner https://xxxx/saml/saml2/idp/metadata.php to logout.
at ComponentSpace.SAML2.AbstractSAMLProvider.CreateLogoutRequest(String logoutReason) in c:\Sandboxes\ComponentSpace\SAMLv20\Library\AbstractSAMLProvider.cs:line 171
at ComponentSpace.SAML2.InternalSAMLServiceProvider.InitiateSLO(HttpResponse httpResponse, String logoutReason, String partnerIdP) in c:\Sandboxes\ComponentSpace\SAMLv20\Library\InternalSAMLService
Provider.cs:line 626
at …


We are the SP in this scenario.
Is there a trick to this? It doesn’t seem to even be making a request to the IDP before failing.

We maintain state including information on each SSO session. When you call SAMLServiceProvider.InitiateSLO and specify the partner identity provider, we check our internal state to see whether there’s been a previous SSO with this identity provider. If there hasn’t been then you see this error.
Please double check that the partner identity provider name you are supplying to the API call is correct and SSO has occurred.
By default, the state information we maintain is stored in the ASP.NET session.
Make sure that you don’t clear the user’s session as part of local logout prior to calling SAMLServiceProvider.InitiateSLO.
If there’s still an issue, please enable SAML trace and email us the generated log file as an attachment. We would need to see SSO followed by the attempted SLO. Thanks.

http://www.componentspace.com/Forums/17/Enabing-SAML-Trace

[quote]
davehutz - 6/23/2014
We have SSO working fine, but SLO is giving us trouble.
We get this error every time:

ComponentSpace.SAML2.Exceptions.SAMLProtocolException: There is no SSO session to partner https://xxxx/saml/saml2/idp/metadata.php to logout.
at ComponentSpace.SAML2.AbstractSAMLProvider.CreateLogoutRequest(String logoutReason) in c:\Sandboxes\ComponentSpace\SAMLv20\Library\AbstractSAMLProvider.cs:line 171
at ComponentSpace.SAML2.InternalSAMLServiceProvider.InitiateSLO(HttpResponse httpResponse, String logoutReason, String partnerIdP) in c:\Sandboxes\ComponentSpace\SAMLv20\Library\InternalSAMLService
Provider.cs:line 626
at ...


We are the SP in this scenario.
Is there a trick to this? It doesn't seem to even be making a request to the IDP before failing.
[/quote]

Hi - I know this post is old. But wanted to know if this issue was resolved. I am also having similar issue.

Please enable SAML trace and send the generated log file as an email attachment to support@componentspace.com mentioning your forum post.
https://www.componentspace.com/Forums/17/Enabing-SAML-Trace
Please include the successful SSO and failing SLO.

I was able to figure it out. As you siggested above, it was related to session. Session was getting abondoned before the call.

I’m glad you found the issue and thanks for letting us know.