Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9851

[GSS] (7.0.z) SAML LogoutResponse includes invalid Responder status

    XMLWordPrintable

Details

    • Hide

      Reproducer notes:

      hit employee
      hit sales-post
      hit employee
      hit employe/?GLO=true

      View LogoutResponse sent from sales-post to idp:

      <samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
      xmlns="urn:oasis:names:tc:SAML:2.0:assertion"
      Destination="http://10.10.178.29:8080/auth/realms/master/protocol/saml"
      ID="ID_c3e91cee-65cb-4652-ad94-e97e69cddbda"
      InResponseTo="ID_a5aa1ad4-d131-4819-b38e-9534050fb722"
      IssueInstant="2017-03-08T17:40:13.119Z"
      Version="2.0"
      >
      <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">http://localhost:8080/sales-post/</saml:Issuer>
      <samlp:Status>
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />
      </samlp:StatusCode>
      </samlp:Status>
      </samlp:LogoutResponse>

      Notice the "Success" tag is inside the "Responder" tag.

      expected:

      <samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
      xmlns="urn:oasis:names:tc:SAML:2.0:assertion"
      Destination="http://10.10.178.29:8080/auth/realms/master/protocol/saml"
      ID="ID_8b350147-9a1c-4192-b95a-ef20b1d72f39"
      InResponseTo="ID_91bc6671-8f07-4cee-ac8e-9fa91ff941bc"
      IssueInstant="2017-03-08T17:50:48.238Z"
      Version="2.0"
      >
      <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">http://localhost:8080/sales-post/</saml:Issuer>
      <samlp:Status>
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />
      </samlp:Status>
      </samlp:LogoutResponse>

      Show
      Reproducer notes: hit employee hit sales-post hit employee hit employe/?GLO=true View LogoutResponse sent from sales-post to idp: <samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns="urn:oasis:names:tc:SAML:2.0:assertion" Destination="http://10.10.178.29:8080/auth/realms/master/protocol/saml" ID="ID_c3e91cee-65cb-4652-ad94-e97e69cddbda" InResponseTo="ID_a5aa1ad4-d131-4819-b38e-9534050fb722" IssueInstant="2017-03-08T17:40:13.119Z" Version="2.0" > <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> http://localhost:8080/sales-post/ </saml:Issuer> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Responder"> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" /> </samlp:StatusCode> </samlp:Status> </samlp:LogoutResponse> Notice the "Success" tag is inside the "Responder" tag. expected: <samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns="urn:oasis:names:tc:SAML:2.0:assertion" Destination="http://10.10.178.29:8080/auth/realms/master/protocol/saml" ID="ID_8b350147-9a1c-4192-b95a-ef20b1d72f39" InResponseTo="ID_91bc6671-8f07-4cee-ac8e-9fa91ff941bc" IssueInstant="2017-03-08T17:50:48.238Z" Version="2.0" > <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"> http://localhost:8080/sales-post/ </saml:Issuer> <samlp:Status> <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" /> </samlp:Status> </samlp:LogoutResponse>
    • EAP 7.0.6

    Description

      PicketLink bug:

      Upon a logoutRequest from an identity server a logoutResponse is generated by the picketlink client with our application that contains that contains a samlp:StatusCode inside a samlp:StatusCode:

      <samlp:Status>
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Responder">
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/></samlp:StatusCode>
      </samlp:Status>

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9677 [GSS] (7.1.0) SAML LogoutResponse includes invalid Responder status

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-9876 [GSS](7.0.z) Upgrade picketlink 2.5.5.SP6 to 2.5.5.SP7

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-dehort Derek Horton
              rnetuka@redhat.com Radovan Netuka
              Ivo Hradek Ivo Hradek (Inactive)
              Ivo Hradek Ivo Hradek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: