Shibboleth Developers

[Halm Reusser <>]

Hi,

we deployed the delegation plugin at a test IdP with success. The deployment 
to another (same configured) IdP failed.

The response we get from the IdP is:

      <saml2p:Response xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol" 
ID="_b695b4c8e6196aede2cbcfe5b607f96a" 
InResponseTo="_fc9db8bfd2e144eed115d1045b61e683" 
IssueInstant="2010-07-21T07:39:22.946Z" Version="2.0">
         <saml2:Issuer xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" 
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity">https://aai-logon.vho-switchaai.ch/idp/shibboleth</saml2:Issuer>
         <saml2p:Status>
            <saml2p:StatusCode 
Value="urn:oasis:names:tc:SAML:2.0:status:Requester"/>
            <saml2p:StatusMessage>No SAML 2.0 Assertion token was 
presented</saml2p:StatusMessage>
         </saml2p:Status>
      </saml2p:Response>

We checked whole debugging / message processing output between the running 
configuration and the breaking configuration, but we didn't found significant 
differences.

Does anyone know how to the debug this in a better way?

09:39:22.946 - WARN 
[edu.internet2.middleware.shibboleth.idp.ext.delegation.profile.LibertyIDWSFSSOSProfileHandler:844] 
- No SAML 2.0 Assertion token was available in the WS-Security context

Many thanks in advance!

-Halm