Why does PicketLink generate SAML LogoutRequest messages that do not contain a Destination attribute?

Solution Unverified - Updated -

Issue

Why does PicketLink generate SAML LogoutRequest messages that do not contain a Destination attribute?

There is an issue with the logout. In the saml logout request the destination is missing, as you can see below:

<samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                     xmlns="urn:oasis:names:tc:SAML:2.0:assertion"
                     ID="ID_5af627ee-0660-44ba-9633-ff2e5b64f28f"
                     IssueInstant="2013-04-29T12:04:05.229Z"
                     Version="2.0"
                     >

The correct one should be like this:

<samlp:LogoutRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                     xmlns="urn:oasis:names:tc:SAML:2.0:assertion"
                     ID="ID_5af627ee-0660-44ba-9633-ff2e5b64f28f"
                     Destination="https://n0.corp.net/nidp/saml2/sso"
                     IssueInstant="2013-04-29T12:04:05.229Z"
                     Version="2.0"
                     >

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.