Uploaded image for project: 'CAS Server'
  1. CAS-949

Missing namespace breaks SamlService functionality

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.4.3.1
    • Fix Version/s: 3.4.9
    • Component/s: Validation
    • Labels:
      None

      Description

      We recently integrated CAS with our hosted e-mail filtering service provider, Postini, using the SAML 1.1 pull process. Their Request document does not include the "samlp:" namespace prefix on the "AssertionArtifact" tag. This causes SamlService.createServiceFrom(...) to break, in that it's parsing the xml as a string, looking for "<samlp:AssertionArtifact>" and "</samlp:AssertionArtifact>". I don't know whether the namespace is strictly required, but CAS could be made more resilient if it parsed that tag using a method that made the "samlp:" prefix optional.

        Attachments

          Activity

            People

            • Assignee:
              battags ScottS
              Reporter:
              phatfingers JohnP
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: