Uploaded image for project: 'OpenSAML - C++'
  1. OpenSAML - C++
  2. CPPOST-112

Implement message correlation in SAML2 encoder/decoder

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0.0, 3.0.1
    • Fix Version/s: 3.1.0
    • Component/s: SAML 1, SAML 2, Security
    • Labels:
      None
    • Operating System:
      Linux
    • CPU Type:
      x86_64
    • C/C++ Compiler:
      GCC 9.x
    • Web Server:
      Apache 2.4

      Description

      Hi Everybody,

       

      I'm facing a really weird behavior inside a specific shibboleth security policy: Bearer policy control.

      According to documentation, it is supposed to perform 4 different checks during the validation of a SAML Response. Among those, the one, object of this issue, is the checkCorrelation control.

      It doesn't work. It is supposed to work by default and is enabled by default, but I can't make it work.

      It basically compares the SAML Response attribute InResponseTo, inside the <samlp response> tag, with the parameter of the same name but contained inside the <saml:SubjectConfirmationData> element.

      If i put inside the <saml:SubjectConfirmationData> tag, InResponseTo attribute, a fake value the checkCorrelation is always true and the SAML Response is not rejected as expected.

      Could you please help me

      Thank you

      Tommaso

       

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cantor.2@osu.edu Scott Cantor
              Reporter:
              cybertech@unitedid.org cybertech@unitedid.org
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 15 minutes
                  2d 15m