Skip to Content.
Sympa Menu

shibboleth-dev - Re: [Shib-Dev] Re: [Shib-Users] IdP Single Logout Support Feedback

Subject: Shibboleth Developers

List archive

Re: [Shib-Dev] Re: [Shib-Users] IdP Single Logout Support Feedback


Chronological Thread 
  • From: André Cruz <>
  • To: <>
  • Subject: Re: [Shib-Dev] Re: [Shib-Users] IdP Single Logout Support Feedback
  • Date: Tue, 17 Nov 2009 17:10:39 +0000

On Nov 17, 2009, at 16:17 , Scott Cantor wrote:

>> SAML:2.0:bindings:HTTP-Artifact - consistent SP crash with logging in
> debug:
>
> Are you sure it's artifact and not SOAP?

You're right. I was comenting out the endpoints in the metadata but it skips
the SAML:2.0:bindings:HTTP-Artifact one.

Adam: is SLO through SAML:2.0:bindings:HTTP-Artifact supported?

I can only find this in the IDP log:

17:05:39.727 - INFO
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SLOProfileHandler:571]
- Cannot get SAML2 SingleLogoutService endpoint for SP
'https://sp1.sso2.sso.bk.sapo.pt/shibboleth' and binding
'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect'.
17:05:39.727 - INFO
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SLOProfileHandler:571]
- Cannot get SAML2 SingleLogoutService endpoint for SP
'https://sp1.sso2.sso.bk.sapo.pt/shibboleth' and binding
'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST'.
17:05:39.727 - INFO
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SLOProfileHandler:761]
- No SAML2 LogoutRequest front-channel endpoint found for entity
'https://sp1.sso2.sso.bk.sapo.pt/shibboleth'
17:05:39.728 - INFO
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SLOProfileHandler:571]
- Cannot get SAML2 SingleLogoutService endpoint for SP
'https://sp1.sso2.sso.bk.sapo.pt/shibboleth' and binding
'urn:oasis:names:tc:SAML:2.0:bindings:SOAP'.

>> #6 0x00002b9ad1743e02 in opensaml::saml2p::SAML2SOAPDecoder::decode ()
> from
>> /usr/local/shib-sp2/lib/libsaml.so.6
>
> Hmm, that's not the right decoder, so there'd have to be some seriously
> screwed up internals for that to be artifact. Also, I need the line number.
> There's no bug that I can see in the obvious spot (it checks for null when
> it logs), which reinforces "something's wrong with the build" as a possible
> cause.

I'll build a debug version to see if I can find the line numbers.

André




Archive powered by MHonArc 2.6.16.

Top of Page